linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hyunchul Lee <hyc.lee@gmail.com>,
	Steve French <sfrench@samba.org>,
	David Howells <dhowells@redhat.com>
Cc: kbuild-all@lists.01.org, kernel-team@lge.com,
	Namjae Jeon <linkinjeon@kernel.org>,
	linux-kernel@vger.kernel.org, linux-cifs@vger.kernel.org,
	samba-technical@lists.samba.org, Hyunchul Lee <hyc.lee@gmail.com>
Subject: Re: [PATCH v2] cifs: decoding negTokenInit with generic ASN1 decoder
Date: Sun, 23 May 2021 04:12:43 +0800	[thread overview]
Message-ID: <202105230423.vw2MlhSQ-lkp@intel.com> (raw)
In-Reply-To: <20210521020051.196434-1-hyc.lee@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

Hi Hyunchul,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on cifs/for-next]
[also build test WARNING on linux/master linus/master v5.13-rc2 next-20210521]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Hyunchul-Lee/cifs-decoding-negTokenInit-with-generic-ASN1-decoder/20210522-232614
base:   git://git.samba.org/sfrench/cifs-2.6.git for-next
config: i386-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/e1097df7e174530fece6a8afc49d61d34b904869
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Hyunchul-Lee/cifs-decoding-negTokenInit-with-generic-ASN1-decoder/20210522-232614
        git checkout e1097df7e174530fece6a8afc49d61d34b904869
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> fs/cifs/asn1.c:11:1: warning: no previous prototype for 'decode_negTokenInit' [-Wmissing-prototypes]
      11 | decode_negTokenInit(unsigned char *security_blob, int length,
         | ^~~~~~~~~~~~~~~~~~~


vim +/decode_negTokenInit +11 fs/cifs/asn1.c

     9	
    10	int
  > 11	decode_negTokenInit(unsigned char *security_blob, int length,
    12			    struct TCP_Server_Info *server)
    13	{
    14		if (asn1_ber_decoder(&spnego_negtokeninit_decoder, server,
    15				     security_blob, length) == 0)
    16			return 1;
    17		else
    18			return 0;
    19	}
    20	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29235 bytes --]

  parent reply	other threads:[~2021-05-22 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  2:00 [PATCH v2] cifs: decoding negTokenInit with generic ASN1 decoder Hyunchul Lee
2021-05-21  8:43 ` Aurélien Aptel
2021-05-22 14:17   ` Hyunchul Lee
2021-05-23  2:36   ` Steve French
2021-05-22 20:12 ` kernel test robot [this message]
2021-05-22 21:47 ` kernel test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202105230423.vw2MlhSQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=hyc.lee@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel-team@lge.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).