From: kernel test robot <lkp@intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Tejun Heo <tj@kernel.org>
Subject: [tj-wq:for-7.1-fixes 1/1] kernel/workqueue.c:5916:53: warning: diagnostic behavior may be improved by adding the 'format(printf, 1, 0)' attribute to the declaration of 'alloc_workqueue_va'
Date: Thu, 30 Apr 2026 03:17:09 +0800 [thread overview]
Message-ID: <202604300347.2LgXyteh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-7.1-fixes
head: 0de4cb473aed57ee4ba7e0551ad27bddc19fc519
commit: 0de4cb473aed57ee4ba7e0551ad27bddc19fc519 [1/1] workqueue: fix devm_alloc_workqueue() va_list misuse
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20260430/202604300347.2LgXyteh-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604300347.2LgXyteh-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/202604300347.2LgXyteh-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/workqueue.c:5916:53: warning: diagnostic behavior may be improved by adding the 'format(printf, 1, 0)' attribute to the declaration of 'alloc_workqueue_va' [-Wmissing-format-attribute]
5909 | static struct workqueue_struct *alloc_workqueue_va(const char *fmt,
| __attribute__((format(printf, 1, 0)))
5910 | unsigned int flags,
5911 | int max_active,
5912 | va_list args)
5913 | {
5914 | struct workqueue_struct *wq;
5915 |
5916 | wq = __alloc_workqueue(fmt, flags, max_active, args);
| ^
kernel/workqueue.c:5909:33: note: 'alloc_workqueue_va' declared here
5909 | static struct workqueue_struct *alloc_workqueue_va(const char *fmt,
| ^
1 warning generated.
vim +5916 kernel/workqueue.c
5908
5909 static struct workqueue_struct *alloc_workqueue_va(const char *fmt,
5910 unsigned int flags,
5911 int max_active,
5912 va_list args)
5913 {
5914 struct workqueue_struct *wq;
5915
> 5916 wq = __alloc_workqueue(fmt, flags, max_active, args);
5917 if (wq)
5918 wq_init_lockdep(wq);
5919
5920 return wq;
5921 }
5922
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-29 19:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202604300347.2LgXyteh-lkp@intel.com \
--to=lkp@intel.com \
--cc=leitao@debian.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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