From: kernel test robot <[email protected]>
To: Peter Zijlstra <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
[email protected],
Thomas Gleixner <[email protected]>
Subject: [ammarfaizi2-block:tglx/devel/depthtracking 57/59] kernel/trace/trace_selftest.c:790:13: error: expected string literal before 'CALL_DEPTH_ACCOUNT'
Date: Wed, 3 Aug 2022 18:11:11 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block tglx/devel/depthtracking
head: b518e558c49324fa002255761d2a7324ba31f7b5
commit: cb5c190267562764025e25c3e726ae511003b0a0 [57/59] x86/ftrace: Make it call depth tracking aware
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20220803/[email protected]/config)
compiler: s390-linux-gcc (GCC) 12.1.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/ammarfaizi2/linux-block/commit/cb5c190267562764025e25c3e726ae511003b0a0
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block tglx/devel/depthtracking
git checkout cb5c190267562764025e25c3e726ae511003b0a0
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
All errors (new ones prefixed by >>):
kernel/trace/trace.c: In function 'trace_check_vprintf':
kernel/trace/trace.c:3846:17: warning: function 'trace_check_vprintf' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
3846 | trace_seq_vprintf(&iter->seq, iter->fmt, ap);
| ^~~~~~~~~~~~~~~~~
kernel/trace/trace.c:3913:17: warning: function 'trace_check_vprintf' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
3913 | trace_seq_vprintf(&iter->seq, p, ap);
| ^~~~~~~~~~~~~~~~~
In file included from kernel/trace/trace.c:8672:
kernel/trace/trace_selftest.c: In function 'trace_direct_tramp':
>> kernel/trace/trace_selftest.c:790:13: error: expected string literal before 'CALL_DEPTH_ACCOUNT'
790 | asm(CALL_DEPTH_ACCOUNT);
| ^~~~~~~~~~~~~~~~~~
vim +/CALL_DEPTH_ACCOUNT +790 kernel/trace/trace_selftest.c
786
787 #ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
788 noinline __noclone static void trace_direct_tramp(void)
789 {
> 790 asm(CALL_DEPTH_ACCOUNT);
791 }
792 #endif
793
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-03 10:12 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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