From: kernel test robot <lkp@intel.com>
To: Li Lingfeng <lilingfeng3@huawei.com>,
trondmy@kernel.org, anna@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, jlayton@kernel.org,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai1@huaweicloud.com, houtao1@huawei.com, yi.zhang@huawei.com,
yangerkun@huawei.com, lilingfeng@huaweicloud.com,
lilingfeng3@huawei.com
Subject: Re: [PATCH] nfs: protect nfs41_impl_id by rcu
Date: Thu, 29 Aug 2024 07:16:52 +0800 [thread overview]
Message-ID: <202408290616.QG17h6tl-lkp@intel.com> (raw)
In-Reply-To: <20240828044933.676898-1-lilingfeng3@huawei.com>
Hi Li,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trondmy-nfs/linux-next]
[also build test WARNING on linus/master v6.11-rc5 next-20240828]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Li-Lingfeng/nfs-protect-nfs41_impl_id-by-rcu/20240828-124056
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link: https://lore.kernel.org/r/20240828044933.676898-1-lilingfeng3%40huawei.com
patch subject: [PATCH] nfs: protect nfs41_impl_id by rcu
config: x86_64-randconfig-121-20240829 (https://download.01.org/0day-ci/archive/20240829/202408290616.QG17h6tl-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240829/202408290616.QG17h6tl-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/202408290616.QG17h6tl-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/nfs/nfs4client.c:296:18: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *objp @@ got struct nfs41_impl_id [noderef] __rcu *cl_implid @@
fs/nfs/nfs4client.c:296:18: sparse: expected void const *objp
fs/nfs/nfs4client.c:296:18: sparse: got struct nfs41_impl_id [noderef] __rcu *cl_implid
vim +296 fs/nfs/nfs4client.c
ec409897e7c715 Bryan Schumaker 2012-07-16 283
ec409897e7c715 Bryan Schumaker 2012-07-16 284 static void nfs4_shutdown_client(struct nfs_client *clp)
ec409897e7c715 Bryan Schumaker 2012-07-16 285 {
ec409897e7c715 Bryan Schumaker 2012-07-16 286 if (__test_and_clear_bit(NFS_CS_RENEWD, &clp->cl_res_state))
ec409897e7c715 Bryan Schumaker 2012-07-16 287 nfs4_kill_renewd(clp);
abf79bb341bf52 Chuck Lever 2013-08-09 288 clp->cl_mvops->shutdown_client(clp);
ec409897e7c715 Bryan Schumaker 2012-07-16 289 nfs4_destroy_callback(clp);
ec409897e7c715 Bryan Schumaker 2012-07-16 290 if (__test_and_clear_bit(NFS_CS_IDMAP, &clp->cl_res_state))
ec409897e7c715 Bryan Schumaker 2012-07-16 291 nfs_idmap_delete(clp);
ec409897e7c715 Bryan Schumaker 2012-07-16 292
ec409897e7c715 Bryan Schumaker 2012-07-16 293 rpc_destroy_wait_queue(&clp->cl_rpcwaitq);
ec409897e7c715 Bryan Schumaker 2012-07-16 294 kfree(clp->cl_serverowner);
ec409897e7c715 Bryan Schumaker 2012-07-16 295 kfree(clp->cl_serverscope);
ec409897e7c715 Bryan Schumaker 2012-07-16 @296 kfree(clp->cl_implid);
ceb3a16c070c40 Trond Myklebust 2015-01-03 297 kfree(clp->cl_owner_id);
ec409897e7c715 Bryan Schumaker 2012-07-16 298 }
ec409897e7c715 Bryan Schumaker 2012-07-16 299
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-08-28 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 4:49 Li Lingfeng
2024-08-28 23:16 ` kernel test robot [this message]
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=202408290616.QG17h6tl-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna@kernel.org \
--cc=houtao1@huawei.com \
--cc=jlayton@kernel.org \
--cc=lilingfeng3@huawei.com \
--cc=lilingfeng@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=trondmy@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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
all inboxes | Powered by JetHome®