From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Simon Horman <horms@kernel.org>, Jeff Layton <jlayton@kernel.org>,
Anna Schumaker <anna.schumaker@oracle.com>,
Chuck Lever <chuck.lever@oracle.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Arnd Bergmann <arnd@arndb.de>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Yury Norov <ynorov@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: remove __printf() attribute on __ftrace_vbprintk()
Date: Tue, 3 Feb 2026 20:12:57 +0800 [thread overview]
Message-ID: <202602032036.FQK7gJvV-lkp@intel.com> (raw)
In-Reply-To: <20260202095834.1328352-1-arnd@kernel.org>
Hi Arnd,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20260130]
[cannot apply to trace/for-next linus/master v6.19-rc8 v6.19-rc7 v6.19-rc6 v6.19-rc8]
[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/Arnd-Bergmann/tracing-remove-__printf-attribute-on-__ftrace_vbprintk/20260202-180958
base: next-20260130
patch link: https://lore.kernel.org/r/20260202095834.1328352-1-arnd%40kernel.org
patch subject: [PATCH] tracing: remove __printf() attribute on __ftrace_vbprintk()
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20260203/202602032036.FQK7gJvV-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260203/202602032036.FQK7gJvV-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/202602032036.FQK7gJvV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_printk.c:212:34: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of '__trace_bprintk' [-Wmissing-format-attribute]
212 | ret = trace_vbprintk(ip, fmt, ap);
| ^
include/linux/trace_printk.h:110:5: note: '__trace_bprintk' declared here
110 | int __trace_bprintk(unsigned long ip, const char *fmt, ...);
| ^
1 warning generated.
vim +212 kernel/trace/trace_printk.c
1ba28e02a18cbd kernel/trace/trace_bprintk.c Lai Jiangshan 2009-03-06 199
48ead02030f849 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-12 200 int __trace_bprintk(unsigned long ip, const char *fmt, ...)
1427cdf0592368 kernel/trace/trace_bprintk.c Lai Jiangshan 2009-03-06 201 {
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 202 int ret;
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 203 va_list ap;
1427cdf0592368 kernel/trace/trace_bprintk.c Lai Jiangshan 2009-03-06 204
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 205 if (unlikely(!fmt))
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 206 return 0;
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 207
b9f9108cad3998 kernel/trace/trace_printk.c Steven Rostedt (Red Hat 2015-09-29 208) if (!trace_printk_enabled)
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 209 return 0;
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 210
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 211 va_start(ap, fmt);
40ce74f19c2807 kernel/trace/trace_printk.c Steven Rostedt 2009-03-19 @212 ret = trace_vbprintk(ip, fmt, ap);
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 213 va_end(ap);
769b0441f438c4 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-06 214 return ret;
1427cdf0592368 kernel/trace/trace_bprintk.c Lai Jiangshan 2009-03-06 215 }
48ead02030f849 kernel/trace/trace_printk.c Frederic Weisbecker 2009-03-12 216 EXPORT_SYMBOL_GPL(__trace_bprintk);
1427cdf0592368 kernel/trace/trace_bprintk.c Lai Jiangshan 2009-03-06 217
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2026-02-03 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260202095834.1328352-1-arnd@kernel.org>
2026-02-03 12:12 ` kernel test robot [this message]
2026-02-03 14:58 ` Andy Shevchenko
2026-02-03 15:56 ` Arnd Bergmann
2026-02-03 17:17 ` Andy Shevchenko
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=202602032036.FQK7gJvV-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anna.schumaker@oracle.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=horms@kernel.org \
--cc=jlayton@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=ynorov@nvidia.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