All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@hammerspace.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
	Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>,
	Eric Biggers <ebiggers@kernel.org>,
	Rick Macklem <rick.macklem@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH v1 2/4] nfsd: Add a key for signing filehandles
Date: Sat, 17 Jan 2026 05:37:03 +0800	[thread overview]
Message-ID: <202601170520.GITVT8Iy-lkp@intel.com> (raw)
In-Reply-To: <c49d28aade36c044f0533d03b564ff65e00d9e05.1768573690.git.bcodding@hammerspace.com>

Hi Benjamin,

kernel test robot noticed the following build warnings:

[auto build test WARNING on bfd453acb5637b5df881cef4b21803344aa9e7ac]

url:    https://github.com/intel-lab-lkp/linux/commits/Benjamin-Coddington/nfsd-Convert-export-flags-to-use-BIT-macro/20260116-223927
base:   bfd453acb5637b5df881cef4b21803344aa9e7ac
patch link:    https://lore.kernel.org/r/c49d28aade36c044f0533d03b564ff65e00d9e05.1768573690.git.bcodding%40hammerspace.com
patch subject: [PATCH v1 2/4] nfsd: Add a key for signing filehandles
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260117/202601170520.GITVT8Iy-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260117/202601170520.GITVT8Iy-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601170520.GITVT8Iy-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> fs/nfsd/nfsctl.c:2282:50: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
    2282 |         trace_nfsd_ctl_fh_key_set((const char *)fh_key, ret);
         |                                                         ^~~
   fs/nfsd/nfsctl.c:2260:9: note: initialize the variable 'ret' to silence this warning
    2260 |         int ret;
         |                ^
         |                 = 0
   1 warning generated.


vim +/ret +2282 fs/nfsd/nfsctl.c

  2254	
  2255	int nfsd_nl_fh_key_set_doit(struct sk_buff *skb, struct genl_info *info)
  2256	{
  2257		siphash_key_t *fh_key;
  2258		struct nfsd_net *nn;
  2259		int fh_key_len;
  2260		int ret;
  2261	
  2262		if (GENL_REQ_ATTR_CHECK(info, NFSD_A_SERVER_FH_KEY))
  2263			return -EINVAL;
  2264	
  2265		fh_key_len = nla_len(info->attrs[NFSD_A_SERVER_FH_KEY]);
  2266		if (fh_key_len != sizeof(siphash_key_t))
  2267			return -EINVAL;
  2268	
  2269		/* Is the key already set? */
  2270		nn = net_generic(genl_info_net(info), nfsd_net_id);
  2271		if (nn->fh_key)
  2272			return -EEXIST;
  2273	
  2274		fh_key = kmalloc(sizeof(siphash_key_t), GFP_KERNEL);
  2275		if (!fh_key)
  2276			return -ENOMEM;
  2277	
  2278		memcpy(fh_key, nla_data(info->attrs[NFSD_A_SERVER_FH_KEY]), sizeof(siphash_key_t));
  2279		nn = net_generic(genl_info_net(info), nfsd_net_id);
  2280		nn->fh_key = fh_key;
  2281	
> 2282		trace_nfsd_ctl_fh_key_set((const char *)fh_key, ret);
  2283		return ret;
  2284	}
  2285	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-01-16 21:37 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 14:32 [PATCH v1 0/4] kNFSD Signed Filehandles Benjamin Coddington
2026-01-16 14:32 ` [PATCH v1 1/4] nfsd: Convert export flags to use BIT() macro Benjamin Coddington
2026-01-16 15:31   ` Chuck Lever
2026-01-16 15:35     ` Benjamin Coddington
2026-01-16 15:38       ` Chuck Lever
2026-01-16 15:39         ` Benjamin Coddington
2026-01-16 14:32 ` [PATCH v1 2/4] nfsd: Add a key for signing filehandles Benjamin Coddington
2026-01-16 14:59   ` Jeff Layton
2026-01-16 15:09     ` Chuck Lever
2026-01-16 15:18       ` Benjamin Coddington
2026-01-16 15:25       ` Jeff Layton
2026-01-16 15:45         ` Chuck Lever
2026-01-16 15:52           ` Jeff Layton
2026-01-16 16:17             ` Chuck Lever
2026-01-19 16:15     ` Benjamin Coddington
2026-01-16 16:11   ` Chuck Lever
2026-01-16 16:42     ` Benjamin Coddington
2026-01-16 19:55       ` Chuck Lever
2026-01-16 21:37   ` kernel test robot [this message]
2026-01-16 14:32 ` [PATCH v1 3/4] NFSD/export: Add sign_fh export option Benjamin Coddington
2026-01-16 16:26   ` Chuck Lever
2026-01-16 14:32 ` [PATCH v1 4/4] NFSD: Sign filehandles Benjamin Coddington
2026-01-16 17:12   ` Chuck Lever
2026-01-16 18:29     ` Benjamin Coddington
2026-01-16 22:47   ` kernel test robot
2026-01-16 16:56 ` [PATCH v1 0/4] kNFSD Signed Filehandles Chuck Lever
2026-01-16 17:17   ` Benjamin Coddington
2026-01-16 19:43     ` Chuck Lever
2026-01-16 20:03       ` Trond Myklebust
2026-01-16 20:11       ` Benjamin Coddington
2026-01-17  0:54 ` [PATCH v1 4/4] NFSD: Sign filehandles NeilBrown
2026-01-17 12:30   ` Benjamin Coddington
2026-01-17  1:24 ` [PATCH v1 0/4] kNFSD Signed Filehandles NeilBrown
2026-01-17 12:30   ` Benjamin Coddington
2026-01-19  4:24     ` NeilBrown
2026-01-19  9:14 ` Christian Brauner
2026-01-19 21:06   ` NeilBrown
2026-01-19 21:29     ` Jeff Layton
2026-01-19 22:58       ` NeilBrown
2026-01-20  9:23     ` Christian Brauner
2026-01-20  9:46       ` NeilBrown
2026-01-20 10:20         ` Christian Brauner
2026-01-20 10:28           ` NeilBrown
2026-01-20 10:37             ` Christian Brauner
2026-01-20 10:13 ` NeilBrown
2026-01-20 12:56   ` Benjamin Coddington
2026-01-20 10:55 ` Miklos Szeredi
2026-01-20 13:03   ` Benjamin Coddington
2026-01-20 14:44     ` Miklos Szeredi

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=202601170520.GITVT8Iy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anna@kernel.org \
    --cc=bcodding@hammerspace.com \
    --cc=chuck.lever@oracle.com \
    --cc=ebiggers@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=neil@brown.name \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rick.macklem@gmail.com \
    --cc=trondmy@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.