From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jlayton:dir-deleg 15/26] fs/nfsd/nfs4xdr.c:4109:18: sparse: sparse: incorrect type in assignment (different base types)
Date: Wed, 01 Apr 2026 03:23:08 +0800 [thread overview]
Message-ID: <202604010359.hffRSjbm-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git dir-deleg
head: 23dab10e6368fed23984781ef9a247fc242498da
commit: 17ead909b8fe2314cec2ea3ffe9ccc2492c9c3c9 [15/26] nfsd: add notification handlers for dir events
config: csky-randconfig-r111-20260331 (https://download.01.org/0day-ci/archive/20260401/202604010359.hffRSjbm-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 15.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260401/202604010359.hffRSjbm-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/202604010359.hffRSjbm-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/nfsd/nfs4xdr.c:4109:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] *attrmask @@ got restricted __be32 [usertype] * @@
fs/nfsd/nfs4xdr.c:4109:18: sparse: expected unsigned int [usertype] *attrmask
fs/nfsd/nfs4xdr.c:4109:18: sparse: got restricted __be32 [usertype] *
vim +4109 fs/nfsd/nfs4xdr.c
4100
4101 static bool
4102 nfsd4_setup_notify_entry4(struct notify_entry4 *ne, struct xdr_stream *xdr,
4103 struct dentry *dentry, struct nfs4_delegation *dp,
4104 struct nfsd_file *nf, char *name, u32 namelen)
4105 {
4106 uint32_t *attrmask;
4107
4108 /* Reserve space for attrmask */
> 4109 attrmask = xdr_reserve_space(xdr, 3 * sizeof(uint32_t));
4110 if (!attrmask)
4111 return false;
4112
4113 ne->ne_file.data = name;
4114 ne->ne_file.len = namelen;
4115 ne->ne_attrs.attrmask.element = attrmask;
4116
4117 attrmask[0] = 0;
4118 attrmask[1] = 0;
4119 attrmask[2] = 0;
4120 ne->ne_attrs.attr_vals.data = NULL;
4121 ne->ne_attrs.attr_vals.len = 0;
4122 ne->ne_attrs.attrmask.count = 1;
4123 return true;
4124 }
4125
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-31 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202604010359.hffRSjbm-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.