From: kernel test robot <lkp@intel.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mhiramat:topic/wprobe-v2 8/11] kernel/trace/trace_wprobe.c:230:16: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Mon, 03 Aug 2026 14:10:53 +0800 [thread overview]
Message-ID: <202608031425.kS00ixRr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git topic/wprobe-v2
head: a4397d5c0abf35acc79a3324139364deaf5883ec
commit: d83c23ec2a39f1ae346bbce351cb004be5c58c1e [8/11] tracing: wprobe: Add wprobe event trigger
config: x86_64-randconfig-123-20260803 (https://download.01.org/0day-ci/archive/20260803/202608031425.kS00ixRr-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260803/202608031425.kS00ixRr-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/202608031425.kS00ixRr-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/trace/trace_wprobe.c:230:16: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct perf_event **pevent @@ got struct perf_event *[noderef] __percpu * @@
kernel/trace/trace_wprobe.c:230:16: sparse: expected struct perf_event **pevent
kernel/trace/trace_wprobe.c:230:16: sparse: got struct perf_event *[noderef] __percpu *
>> kernel/trace/trace_wprobe.c:234:15: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct perf_event ** @@
kernel/trace/trace_wprobe.c:234:15: sparse: expected void const [noderef] __percpu *__vpp_verify
kernel/trace/trace_wprobe.c:234:15: sparse: got struct perf_event **
vim +230 kernel/trace/trace_wprobe.c
225
226 static int trace_wprobe_update_local(struct trace_wprobe *tw, unsigned long addr)
227 {
228 struct perf_event **pevent, *bp;
229
> 230 pevent = READ_ONCE(tw->bp_event);
231 if (!pevent)
232 return -EINVAL;
233
> 234 bp = *this_cpu_ptr(pevent);
235 if (!bp)
236 return -EINVAL;
237
238 return modify_local_hw_breakpoint_addr(bp, addr);
239 }
240
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-03 6:11 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 \
--in-reply-to=202608031425.kS00ixRr-lkp@intel.com \
--to=lkp@intel.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.