All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Benson Leung <bleung@chromium.org>,
	Tzung-Bi Shih <tzungbi@kernel.org>,
	Guenter Roeck <groeck@chromium.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	David Woodhouse <dwmw@amazon.co.uk>, Jann Horn <jannh@google.com>,
	Kees Cook <kees@kernel.org>, Breno Leitao <leitao@debian.org>,
	chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Ingo Molnar <mingo@redhat.com>,
	Will Deacon <will@kernel.org>, Boqun Feng <boqun@kernel.org>
Subject: Re: [PATCH] kthread: Teach lockdep about kthread_flush_work() dependencies
Date: Wed, 21 Oct 2026 15:41:08 +0800	[thread overview]
Message-ID: <202610211501.YBj5GUfA-lkp@intel.com> (raw)
In-Reply-To: <6dee36e290c2a3b85dcd7cdba2cab72fe57b25c4.camel@infradead.org>

Hi David,

kernel test robot noticed the following build warnings:

[auto build test WARNING on chrome-platform/for-next]
[also build test WARNING on chrome-platform/for-firmware-next linus/master v7.3 next-20261019]
[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/David-Woodhouse/kthread-Teach-lockdep-about-kthread_flush_work-dependencies/20261020-160400
base:   https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
patch link:    https://lore.kernel.org/r/6dee36e290c2a3b85dcd7cdba2cab72fe57b25c4.camel%40infradead.org
patch subject: [PATCH] kthread: Teach lockdep about kthread_flush_work() dependencies
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20261021/202610211501.YBj5GUfA-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261021/202610211501.YBj5GUfA-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/202610211501.YBj5GUfA-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from kernel/rcu/tree.c:45:
   kernel/rcu/tree_exp.h: In function 'sync_rcu_exp_select_cpus_queue_work':
>> include/linux/kthread.h:219:46: warning: unused variable '__work_key' [-Wunused-variable]
     219 |                 static struct lock_class_key __work_key;                \
         |                                              ^~~~~~~~~~
   kernel/rcu/tree_exp.h:470:9: note: in expansion of macro 'kthread_init_work'
     470 |         kthread_init_work(&rnp->rew.rew_work, sync_rcu_exp_select_node_cpus);
         |         ^~~~~~~~~~~~~~~~~
   kernel/rcu/tree_exp.h: In function 'synchronize_rcu_expedited_queue_work':
>> include/linux/kthread.h:219:46: warning: unused variable '__work_key' [-Wunused-variable]
     219 |                 static struct lock_class_key __work_key;                \
         |                                              ^~~~~~~~~~
   kernel/rcu/tree_exp.h:497:9: note: in expansion of macro 'kthread_init_work'
     497 |         kthread_init_work(&rew->rew_work, wait_rcu_exp_gp);
         |         ^~~~~~~~~~~~~~~~~


vim +/__work_key +219 include/linux/kthread.h

   216	
   217	#define kthread_init_work(work, fn)					\
   218		do {								\
 > 219			static struct lock_class_key __work_key;		\
   220			memset((work), 0, sizeof(struct kthread_work));		\
   221			INIT_LIST_HEAD(&(work)->node);				\
   222			(work)->func = (fn);					\
   223			__kthread_init_work_lockdep_map((work), &__work_key);	\
   224		} while (0)
   225	

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

  reply	other threads:[~2026-10-21  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 15:04 [PATCH] kthread: Teach lockdep about kthread_flush_work() dependencies David Woodhouse
2026-10-21  7:41 ` kernel test robot [this message]
2026-10-21  9:55 ` kernel test robot

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=202610211501.YBj5GUfA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bleung@chromium.org \
    --cc=boqun@kernel.org \
    --cc=brauner@kernel.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dwmw2@infradead.org \
    --cc=dwmw@amazon.co.uk \
    --cc=frederic@kernel.org \
    --cc=groeck@chromium.org \
    --cc=jannh@google.com \
    --cc=kees@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tzungbi@kernel.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.