From: Waiman Long <longman@redhat.com>
To: kernel test robot <lkp@intel.com>, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
Cestmir Kalina <ckalina@redhat.com>,
Alex Gladkov <agladkov@redhat.com>, Phil Auld <pauld@redhat.com>,
Costa Shulyupin <cshulyup@redhat.com>
Subject: Re: [PATCH-wq v2 3/5] workqueue: Thaw frozen pwq in workqueue_apply_unbound_cpumask()
Date: Sun, 4 Feb 2024 11:07:17 -0500 [thread overview]
Message-ID: <149cbb48-ad60-4817-b464-ad53418aadd0@redhat.com> (raw)
In-Reply-To: <202402041854.YeHAF3wV-lkp@intel.com>
On 2/4/24 05:15, kernel test robot wrote:
> Hi Waiman,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on tj-wq/for-next]
> [also build test WARNING on next-20240202]
> [cannot apply to linus/master v6.8-rc2]
> [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/Waiman-Long/workqueue-Skip-__WQ_DESTROYING-workqueues-when-updating-global-unbound-cpumask/20240203-234626
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-next
> patch link: https://lore.kernel.org/r/20240203154334.791910-4-longman%40redhat.com
> patch subject: [PATCH-wq v2 3/5] workqueue: Thaw frozen pwq in workqueue_apply_unbound_cpumask()
> config: x86_64-randconfig-122-20240204 (https://download.01.org/0day-ci/archive/20240204/202402041854.YeHAF3wV-lkp@intel.com/config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240204/202402041854.YeHAF3wV-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/202402041854.YeHAF3wV-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> kernel/workqueue.c:361:40: sparse: sparse: duplicate [noderef]
> kernel/workqueue.c:361:40: sparse: sparse: multiple address spaces given: __percpu & __rcu
>>> kernel/workqueue.c:6373:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
> kernel/workqueue.c:6373:25: sparse: struct pool_workqueue *
> kernel/workqueue.c:6373:25: sparse: struct pool_workqueue [noderef] __rcu *
OK, I didn't realize that a __rcu tag is added to the dfl_pwq in 6.9.
Will change the patch series to use the appropriate helpers to avoid
this kind of warnings.
Cheers,
Longman
next prev parent reply other threads:[~2024-02-04 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 15:43 [PATCH-wq v2 0/5] workqueue: Enable unbound cpumask update on ordered workqueues Waiman Long
2024-02-03 15:43 ` [PATCH-wq v2 1/5] workqueue: Skip __WQ_DESTROYING workqueues when updating global unbound cpumask Waiman Long
2024-02-05 18:00 ` Tejun Heo
2024-02-03 15:43 ` [PATCH-wq v2 2/5] workqueue: Enable unbound cpumask update on ordered workqueues Waiman Long
2024-02-05 19:23 ` Tejun Heo
2024-02-03 15:43 ` [PATCH-wq v2 3/5] workqueue: Thaw frozen pwq in workqueue_apply_unbound_cpumask() Waiman Long
2024-02-04 10:15 ` kernel test robot
2024-02-04 16:07 ` Waiman Long [this message]
2024-02-03 15:43 ` [PATCH-wq v2 4/5] kernel/workqueue: Let rescuers follow unbound wq cpumask changes Waiman Long
2024-02-03 15:43 ` [PATCH-wq v2 5/5] workqueue: Bind unbound workqueue rescuer to wq_unbound_cpumask Waiman Long
2024-02-05 9:48 ` [PATCH-wq v2 0/5] workqueue: Enable unbound cpumask update on ordered workqueues Juri Lelli
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=149cbb48-ad60-4817-b464-ad53418aadd0@redhat.com \
--to=longman@redhat.com \
--cc=agladkov@redhat.com \
--cc=ckalina@redhat.com \
--cc=cshulyup@redhat.com \
--cc=jiangshanlai@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pauld@redhat.com \
--cc=tj@kernel.org \
/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®