From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH V2 5/9] tracing/trace: Add a generic function to read/write u64 values from tracefs
Date: Sat, 24 Apr 2021 07:41:10 +0800 [thread overview]
Message-ID: <202104240702.33PbNGd1-lkp@intel.com> (raw)
In-Reply-To: <f708a3c093ecb2f2513813f9d92548f03f6ec0d7.1619210818.git.bristot@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4739 bytes --]
Hi Daniel,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tip/perf/core]
[also build test WARNING on linux/master linus/master v5.12-rc8]
[cannot apply to trace/for-next next-20210423]
[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/Daniel-Bristot-de-Oliveira/hwlat-improvements-and-osnoise-timerlat-tracers/20210424-050958
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ed8e50800bf4c2d904db9c75408a67085e6cca3d
config: x86_64-randconfig-s022-20210423 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/21b6c7475ccbd8c3dd5a0cb291166b7c54366243
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Daniel-Bristot-de-Oliveira/hwlat-improvements-and-osnoise-timerlat-tracers/20210424-050958
git checkout 21b6c7475ccbd8c3dd5a0cb291166b7c54366243
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
kernel/trace/trace.c:383:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct trace_export **list @@ got struct trace_export [noderef] __rcu ** @@
kernel/trace/trace.c:383:28: sparse: expected struct trace_export **list
kernel/trace/trace.c:383:28: sparse: got struct trace_export [noderef] __rcu **
kernel/trace/trace.c:397:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct trace_export **list @@ got struct trace_export [noderef] __rcu ** @@
kernel/trace/trace.c:397:33: sparse: expected struct trace_export **list
kernel/trace/trace.c:397:33: sparse: got struct trace_export [noderef] __rcu **
kernel/trace/trace.c:2797:38: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct event_filter *filter @@ got struct event_filter [noderef] __rcu *filter @@
kernel/trace/trace.c:2797:38: sparse: expected struct event_filter *filter
kernel/trace/trace.c:2797:38: sparse: got struct event_filter [noderef] __rcu *filter
kernel/trace/trace.c:3132:46: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct trace_buffer_struct * @@
kernel/trace/trace.c:3132:46: sparse: expected void const [noderef] __percpu *__vpp_verify
kernel/trace/trace.c:3132:46: sparse: got struct trace_buffer_struct *
kernel/trace/trace.c:3148:9: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got int * @@
kernel/trace/trace.c:3148:9: sparse: expected void const [noderef] __percpu *__vpp_verify
kernel/trace/trace.c:3148:9: sparse: got int *
kernel/trace/trace.c:3158:17: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct trace_buffer_struct *buffers @@ got struct trace_buffer_struct [noderef] __percpu * @@
kernel/trace/trace.c:3158:17: sparse: expected struct trace_buffer_struct *buffers
kernel/trace/trace.c:3158:17: sparse: got struct trace_buffer_struct [noderef] __percpu *
>> kernel/trace/trace.c:7301:1: sparse: sparse: symbol 'trace_ull_config_write' was not declared. Should it be static?
>> kernel/trace/trace.c:7348:1: sparse: sparse: symbol 'trace_ull_config_read' was not declared. Should it be static?
kernel/trace/trace.c:337:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/trace/trace.c:337:9: sparse: struct trace_export [noderef] __rcu *
kernel/trace/trace.c:337:9: sparse: struct trace_export *
kernel/trace/trace.c:352:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/trace/trace.c:352:9: sparse: struct trace_export [noderef] __rcu *
kernel/trace/trace.c:352:9: sparse: struct trace_export *
Please review and possibly fold the followup patch.
---
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: 32125 bytes --]
next prev parent reply other threads:[~2021-04-23 23:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 21:05 [RFC PATCH V2 0/9] hwlat improvements and osnoise/timerlat tracers Daniel Bristot de Oliveira
2021-04-23 21:05 ` [RFC PATCH V2 1/9] tracing/hwlat: Fix Clark's email Daniel Bristot de Oliveira
2021-04-23 21:05 ` [RFC PATCH V2 2/9] tracing/hwlat: Implement the mode config option Daniel Bristot de Oliveira
2021-04-23 21:05 ` [RFC PATCH V2 3/9] tracing/hwlat: Switch disable_migrate to mode none Daniel Bristot de Oliveira
2021-04-23 21:05 ` [RFC PATCH V2 4/9] tracing/hwlat: Implement the per-cpu mode Daniel Bristot de Oliveira
2021-04-24 4:43 ` kernel test robot
2021-04-23 21:05 ` [RFC PATCH V2 5/9] tracing/trace: Add a generic function to read/write u64 values from tracefs Daniel Bristot de Oliveira
2021-04-23 23:05 ` kernel test robot
2021-04-23 23:41 ` kernel test robot [this message]
2021-04-23 23:41 ` [RFC PATCH] tracing/trace: trace_ull_config_write can be static kernel test robot
2021-04-23 23:54 ` [RFC PATCH V2 5/9] tracing/trace: Add a generic function to read/write u64 values from tracefs kernel test robot
2021-04-23 21:05 ` [RFC PATCH V2 6/9] tracing/hwlat: Use the generic function to read/write width and window Daniel Bristot de Oliveira
2021-04-23 21:05 ` [RFC PATCH V2 7/9] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers Daniel Bristot de Oliveira
2021-04-23 21:05 ` [RFC PATCH V2 8/9] tracing: Add osnoise tracer Daniel Bristot de Oliveira
2021-04-24 3:48 ` kernel test robot
2021-04-23 21:05 ` [RFC PATCH V2 9/9] tracing: Add timerlat tracer Daniel Bristot de Oliveira
2021-05-14 8:55 ` Juri Lelli
2021-05-14 8:59 ` Daniel Bristot de Oliveira
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=202104240702.33PbNGd1-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.