From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6771/7300] fs/afs/main.c:159:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Wed, 13 Dec 2023 19:22:31 +0800 [thread overview]
Message-ID: <202312131907.mnyTUNnO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 48e8992e33abf054bcc0bb2e77b2d43bb899212e
commit: 83101146668283fa5109921fde006287e0f4e195 [6771/7300] afs: Provide a way to configure address priorities
config: nios2-randconfig-r112-20231213 (https://download.01.org/0day-ci/archive/20231213/202312131907.mnyTUNnO-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231213/202312131907.mnyTUNnO-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/202312131907.mnyTUNnO-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/afs/main.c:159:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct callback_head *head @@ got struct callback_head [noderef] __rcu * @@
fs/afs/main.c:159:9: sparse: expected struct callback_head *head
fs/afs/main.c:159:9: sparse: got struct callback_head [noderef] __rcu *
>> fs/afs/main.c:159:9: sparse: sparse: cast removes address space '__rcu' of expression
vim +159 fs/afs/main.c
144
145 /*
146 * Clean up and destroy an AFS network namespace record.
147 */
148 static void __net_exit afs_net_exit(struct net *net_ns)
149 {
150 struct afs_net *net = afs_net(net_ns);
151
152 net->live = false;
153 afs_fs_probe_cleanup(net);
154 afs_cell_purge(net);
155 afs_purge_servers(net);
156 afs_close_socket(net);
157 afs_proc_cleanup(net);
158 afs_put_sysnames(net->sysnames);
> 159 kfree_rcu(net->address_prefs, rcu);
160 }
161
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-13 11: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=202312131907.mnyTUNnO-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox