public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Wang Jinchao <wangjinchao@xfusion.com>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Daniel Jordan <daniel.m.jordan@oracle.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, stone.xulei@xfusion.com
Subject: Re: [PATCH] padata: Fix the UAF issue related to parallel_data
Date: Wed, 27 Sep 2023 08:42:22 +0800	[thread overview]
Message-ID: <202309270829.xHgTOMKw-lkp@intel.com> (raw)
In-Reply-To: <ZRE4XvOOhz4HSOgR@fedora>

Hi Wang,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc3 next-20230926]
[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/Wang-Jinchao/padata-Fix-the-UAF-issue-related-to-parallel_data/20230925-153852
base:   linus/master
patch link:    https://lore.kernel.org/r/ZRE4XvOOhz4HSOgR%40fedora
patch subject: [PATCH] padata: Fix the UAF issue related to parallel_data
config: i386-randconfig-062-20230925 (https://download.01.org/0day-ci/archive/20230927/202309270829.xHgTOMKw-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230927/202309270829.xHgTOMKw-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/202309270829.xHgTOMKw-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> kernel/padata.c:1110:38: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct refcount_struct [usertype] *r @@     got struct refcount_struct [noderef] __rcu * @@
   kernel/padata.c:1110:38: sparse:     expected struct refcount_struct [usertype] *r
   kernel/padata.c:1110:38: sparse:     got struct refcount_struct [noderef] __rcu *

vim +1110 kernel/padata.c

  1097	
  1098	/**
  1099	 * padata_free_shell - free a padata shell
  1100	 *
  1101	 * @ps: padata shell to free
  1102	 */
  1103	void padata_free_shell(struct padata_shell *ps)
  1104	{
  1105		if (!ps)
  1106			return;
  1107	
  1108		mutex_lock(&ps->pinst->lock);
  1109		list_del(&ps->list);
> 1110		if (refcount_dec_and_test(&ps->pd->refcnt))
  1111			padata_free_pd(rcu_dereference_protected(ps->pd, 1));
  1112		mutex_unlock(&ps->pinst->lock);
  1113	
  1114		kfree(ps);
  1115	}
  1116	EXPORT_SYMBOL(padata_free_shell);
  1117	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2023-09-27  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  7:35 [PATCH] padata: Fix the UAF issue related to parallel_data Wang Jinchao
2023-09-27  0:42 ` 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=202309270829.xHgTOMKw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=daniel.m.jordan@oracle.com \
    --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=stone.xulei@xfusion.com \
    --cc=wangjinchao@xfusion.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