From: kernel test robot <lkp@intel.com>
To: Chen Ridong <chenridong@huaweicloud.com>,
steffen.klassert@secunet.com, daniel.m.jordan@oracle.com,
herbert@gondor.apana.org.au
Cc: oe-kbuild-all@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, chenridong@huawei.com,
wangweiyang2@huawei.com
Subject: Re: [PATCH 1/2] padata: add pd get/put refcnt helper
Date: Tue, 26 Nov 2024 19:04:10 +0800 [thread overview]
Message-ID: <202411261818.iINyAe83-lkp@intel.com> (raw)
In-Reply-To: <20241123080509.2573987-2-chenridong@huaweicloud.com>
Hi Chen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.12 next-20241126]
[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/Chen-Ridong/padata-add-pd-get-put-refcnt-helper/20241125-111043
base: linus/master
patch link: https://lore.kernel.org/r/20241123080509.2573987-2-chenridong%40huaweicloud.com
patch subject: [PATCH 1/2] padata: add pd get/put refcnt helper
config: x86_64-randconfig-122-20241125 (https://download.01.org/0day-ci/archive/20241126/202411261818.iINyAe83-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/20241126/202411261818.iINyAe83-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/202411261818.iINyAe83-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/padata.c:1142:25: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct parallel_data *pd @@ got struct parallel_data [noderef] __rcu *pd @@
kernel/padata.c:1142:25: sparse: expected struct parallel_data *pd
kernel/padata.c:1142:25: sparse: got struct parallel_data [noderef] __rcu *pd
kernel/padata.c: note: in included file (through include/linux/swait.h, include/linux/completion.h):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
vim +1142 kernel/padata.c
1126
1127 /**
1128 * padata_free_shell - free a padata shell
1129 *
1130 * @ps: padata shell to free
1131 */
1132 void padata_free_shell(struct padata_shell *ps)
1133 {
1134 struct parallel_data *pd;
1135
1136 if (!ps)
1137 return;
1138
1139 mutex_lock(&ps->pinst->lock);
1140 list_del(&ps->list);
1141 pd = rcu_dereference_protected(ps->pd, 1);
> 1142 padata_put_pd(ps->pd);
1143 mutex_unlock(&ps->pinst->lock);
1144
1145 kfree(ps);
1146 }
1147 EXPORT_SYMBOL(padata_free_shell);
1148
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-26 11:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 8:05 [PATCH 0/2] padata: fix UAF in padata_reorder Chen Ridong
2024-11-23 8:05 ` [PATCH 1/2] padata: add pd get/put refcnt helper Chen Ridong
2024-11-25 13:17 ` kernel test robot
2024-11-26 11:04 ` kernel test robot [this message]
2024-11-29 8:00 ` chenridong
2024-12-05 23:03 ` Daniel Jordan
2024-12-06 2:13 ` chenridong
2024-11-23 8:05 ` [PATCH 2/2] padata: fix UAF in padata_reorder Chen Ridong
2024-12-05 23:01 ` Daniel Jordan
2024-12-06 3:48 ` chenridong
2024-12-10 9:38 ` Chen Ridong
2024-12-10 19:16 ` Daniel Jordan
2024-12-10 19:12 ` Daniel Jordan
2024-12-23 9:00 ` Chen Ridong
2025-01-07 18:43 ` Daniel Jordan
2025-01-09 7:26 ` Chen Ridong
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=202411261818.iINyAe83-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=daniel.m.jordan@oracle.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steffen.klassert@secunet.com \
--cc=wangweiyang2@huawei.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