From: kernel test robot <lkp@intel.com>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-nfs@vger.kernel.org,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: [trondmy-nfs:testing 27/29] net/sunrpc/debugfs.c:78:21: sparse: sparse: cast removes address space '__rcu' of expression
Date: Wed, 27 Nov 2024 01:14:09 +0800 [thread overview]
Message-ID: <202411270142.dpt7kOPF-lkp@intel.com> (raw)
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
head: 0c72d16cb63da4589029e2e60b0be86ab4def2c4
commit: 47f2d22f3ba33173238cf7e009b931602983157c [27/29] SUNRPC: display total RPC tasks for RPC client
config: i386-randconfig-r133-20241126 (https://download.01.org/0day-ci/archive/20241127/202411270142.dpt7kOPF-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241127/202411270142.dpt7kOPF-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/202411270142.dpt7kOPF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/sunrpc/debugfs.c:78:21: sparse: sparse: cast removes address space '__rcu' of expression
--
>> net/sunrpc/clnt.c:3332:9: sparse: sparse: cast removes address space '__rcu' of expression
vim +/__rcu +78 net/sunrpc/debugfs.c
70
71 static void
72 tasks_stop(struct seq_file *f, void *v)
73 __releases(&clnt->cl_lock)
74 {
75 struct rpc_clnt *clnt = f->private;
76 spin_unlock(&clnt->cl_lock);
77 seq_printf(f, "clnt[%pISpc] RPC tasks[%d]\n",
> 78 (struct sockaddr *)&clnt->cl_xprt->addr,
79 atomic_read(&clnt->cl_task_count));
80 }
81
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-26 17:14 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=202411270142.dpt7kOPF-lkp@intel.com \
--to=lkp@intel.com \
--cc=dai.ngo@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=trond.myklebust@hammerspace.com \
/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