From: kernel test robot <lkp@intel.com>
To: Jeff Xie <xiehuan09@gmail.com>, rostedt@goodmis.org
Cc: kbuild-all@lists.01.org, mingo@redhat.com, mhiramat@kernel.org,
zanussi@kernel.org, linux-kernel@vger.kernel.org,
Jeff Xie <xiehuan09@gmail.com>
Subject: Re: [PATCH v11 1/4] trace: Add trace any kernel object
Date: Fri, 3 Jun 2022 06:05:04 +0800 [thread overview]
Message-ID: <202206030528.0x7yQIj3-lkp@intel.com> (raw)
In-Reply-To: <20220602164518.286295-2-xiehuan09@gmail.com>
Hi Jeff,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on b39181f7c6907dc66ff937b74758671fa6ba430c]
url: https://github.com/intel-lab-lkp/linux/commits/Jeff-Xie/trace-Introduce-objtrace-trigger-to-trace-the-kernel-object/20220603-004723
base: b39181f7c6907dc66ff937b74758671fa6ba430c
config: i386-randconfig-a001 (https://download.01.org/0day-ci/archive/20220603/202206030528.0x7yQIj3-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/765253f020469f94856aedc5a3fe5444e1e8f4e8
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Jeff-Xie/trace-Introduce-objtrace-trigger-to-trace-the-kernel-object/20220603-004723
git checkout 765253f020469f94856aedc5a3fe5444e1e8f4e8
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from include/linux/kernel.h:29,
from arch/x86/include/asm/percpu.h:27,
from arch/x86/include/asm/preempt.h:6,
from include/linux/preempt.h:78,
from include/linux/spinlock.h:55,
from include/linux/wait.h:9,
from include/linux/wait_bit.h:8,
from include/linux/fs.h:6,
from include/linux/seq_buf.h:5,
from include/linux/trace_seq.h:5,
from kernel/trace/trace_output.h:5,
from kernel/trace/trace_object.c:9:
kernel/trace/trace_object.c: In function 'event_object_trigger_parse':
>> include/linux/kern_levels.h:5:25: warning: format '%ld' expects argument of type 'long int', but argument 3 has type 'unsigned int' [-Wformat=]
5 | #define KERN_SOH "\001" /* ASCII Start Of Header */
| ^~~~~~
include/linux/printk.h:418:25: note: in definition of macro 'printk_index_wrap'
418 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~
include/linux/printk.h:489:9: note: in expansion of macro 'printk'
489 | printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~
include/linux/kern_levels.h:11:25: note: in expansion of macro 'KERN_SOH'
11 | #define KERN_ERR KERN_SOH "3" /* error conditions */
| ^~~~~~~~
include/linux/printk.h:489:16: note: in expansion of macro 'KERN_ERR'
489 | printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~
kernel/trace/trace_object.c:336:17: note: in expansion of macro 'pr_err'
336 | pr_err("the size of the %s should be:%ld\n", field->name, sizeof(void *));
| ^~~~~~
vim +5 include/linux/kern_levels.h
314ba3520e513a Joe Perches 2012-07-30 4
04d2c8c83d0e3a Joe Perches 2012-07-30 @5 #define KERN_SOH "\001" /* ASCII Start Of Header */
04d2c8c83d0e3a Joe Perches 2012-07-30 6 #define KERN_SOH_ASCII '\001'
04d2c8c83d0e3a Joe Perches 2012-07-30 7
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-06-02 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 16:45 [PATCH v11 0/4] trace: Introduce objtrace trigger to trace the " Jeff Xie
2022-06-02 16:45 ` [PATCH v11 1/4] trace: Add trace any " Jeff Xie
2022-06-02 21:12 ` kernel test robot
2022-06-03 1:48 ` Jeff Xie
2022-06-03 15:37 ` Nathan Chancellor
2022-06-04 2:19 ` Jeff Xie
2022-06-02 22:05 ` kernel test robot [this message]
2022-06-02 16:45 ` [PATCH v11 2/4] trace/objtrace: Get the value of the object Jeff Xie
2022-06-02 16:45 ` [PATCH v11 3/4] trace/objtrace: Add testcases for objtrace Jeff Xie
2022-06-02 16:45 ` [PATCH v11 4/4] trace/objtrace: Add documentation " Jeff Xie
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=202206030528.0x7yQIj3-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=xiehuan09@gmail.com \
--cc=zanussi@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
all inboxes | Powered by JetHome®