From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 1/3] tracing: Show real address for trace event arguments
Date: Thu, 15 Oct 2020 20:10:39 +0800 [thread overview]
Message-ID: <202010152045.bNEih2Vv-lkp@intel.com> (raw)
In-Reply-To: <160275240824.115066.5442110208796724044.stgit@devnote2>
[-- Attachment #1: Type: text/plain, Size: 2709 bytes --]
Hi Masami,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tip/perf/core]
[also build test WARNING on trace/for-next linus/master linux/master v5.9 next-20201015]
[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]
url: https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/tracing-Show-real-address-instead-of-hashed-pointer/20201015-170221
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git f91072ed1b7283b13ca57fcfbece5a3b92726143
config: mips-randconfig-r032-20201014 (attached as .config)
compiler: mips-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/a6a1d5c58f41dfe757e25790b0183ea0a0ff7754
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Masami-Hiramatsu/tracing-Show-real-address-instead-of-hashed-pointer/20201015-170221
git checkout a6a1d5c58f41dfe757e25790b0183ea0a0ff7754
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
kernel/trace/trace_output.c: In function 'trace_event_printf':
>> kernel/trace/trace_output.c:320:2: warning: function 'trace_event_printf' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
320 | trace_seq_vprintf(&iter->seq, trace_event_format(iter, fmt), ap);
| ^~~~~~~~~~~~~~~~~
kernel/trace/trace_output.c: In function 'trace_output_raw':
kernel/trace/trace_output.c:331:2: warning: function 'trace_output_raw' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
331 | trace_seq_vprintf(s, trace_event_format(iter, fmt), ap);
| ^~~~~~~~~~~~~~~~~
vim +320 kernel/trace/trace_output.c
314
315 void trace_event_printf(struct trace_iterator *iter, const char *fmt, ...)
316 {
317 va_list ap;
318
319 va_start(ap, fmt);
> 320 trace_seq_vprintf(&iter->seq, trace_event_format(iter, fmt), ap);
321 va_end(ap);
322 }
323 EXPORT_SYMBOL(trace_event_printf);
324
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34737 bytes --]
next prev parent reply other threads:[~2020-10-15 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 8:59 [RFC PATCH v2 0/3] tracing: Show real address instead of hashed pointer Masami Hiramatsu
2020-10-15 9:00 ` [RFC PATCH v2 1/3] tracing: Show real address for trace event arguments Masami Hiramatsu
2020-10-15 12:10 ` kernel test robot [this message]
2020-10-15 13:09 ` Steven Rostedt
2020-10-15 13:51 ` Masami Hiramatsu
2020-10-15 9:00 ` [RFC PATCH v2 2/3] tracing: Update the stage 3 of trace event macro comment Masami Hiramatsu
2020-10-15 9:00 ` [RFC PATCH v2 3/3] tracing: Add ptr-hash option to show the hashed pointer value Masami Hiramatsu
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=202010152045.bNEih2Vv-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.