From: kernel test robot <lkp@intel.com>
To: NeilBrown <neilb@suse.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Anna Schumaker <Anna.Schumaker@netapp.com>
Subject: net/sunrpc/auth.c:725:34: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Tue, 26 Dec 2023 10:47:03 +0800 [thread overview]
Message-ID: <202312261006.VIxuWJPi-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fbafc3e621c3f4ded43720fdb1d6ce1728ec664e
commit: 5e16923b432bfe79fdfb7cd95ed8e63f6438b663 NFS/SUNRPC: don't lookup machine credential until rpcauth_bindcred().
date: 5 years ago
config: x86_64-randconfig-003-20231011 (https://download.01.org/0day-ci/archive/20231226/202312261006.VIxuWJPi-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231226/202312261006.VIxuWJPi-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/202312261006.VIxuWJPi-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/sunrpc/auth.c:725:34: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct cred const *cred @@ got struct cred const [noderef] __rcu *extern [addressable] [toplevel] cred @@
net/sunrpc/auth.c:725:34: sparse: expected struct cred const *cred
net/sunrpc/auth.c:725:34: sparse: got struct cred const [noderef] __rcu *extern [addressable] [toplevel] cred
net/sunrpc/auth.c: note: in included file:
include/linux/slab.h:332:43: sparse: sparse: dubious: x & !y
include/linux/slab.h:332:43: sparse: sparse: dubious: x & !y
vim +725 net/sunrpc/auth.c
718
719 static struct rpc_cred *
720 rpcauth_bind_machine_cred(struct rpc_task *task, int lookupflags)
721 {
722 struct rpc_auth *auth = task->tk_client->cl_auth;
723 struct auth_cred acred = {
724 .principal = task->tk_client->cl_principal,
> 725 .cred = init_task.cred,
726 };
727
728 if (!acred.principal)
729 return NULL;
730 dprintk("RPC: %5u looking up %s machine cred\n",
731 task->tk_pid, task->tk_client->cl_auth->au_ops->au_name);
732 return auth->au_ops->lookup_cred(auth, &acred, lookupflags);
733 }
734
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-26 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 2:47 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-25 11:54 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=202312261006.VIxuWJPi-lkp@intel.com \
--to=lkp@intel.com \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®