From: kernel test robot <lkp@intel.com>
To: Menglong Dong <menglong8.dong@gmail.com>, jolsa@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, kpsingh@kernel.org,
mattbobrowski@google.com, song@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, yonghong.song@linux.dev,
john.fastabend@gmail.com, sdf@fomichev.me, haoluo@google.com,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: remove is_return in struct bpf_session_run_ctx
Date: Tue, 23 Sep 2025 15:52:05 +0800 [thread overview]
Message-ID: <202509231550.BWhLcP9e-lkp@intel.com> (raw)
In-Reply-To: <20250922095705.252519-1-dongml2@chinatelecom.cn>
Hi Menglong,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Menglong-Dong/bpf-remove-is_return-in-struct-bpf_session_run_ctx/20250922-175833
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20250922095705.252519-1-dongml2%40chinatelecom.cn
patch subject: [PATCH bpf-next] bpf: remove is_return in struct bpf_session_run_ctx
config: i386-randconfig-r113-20250923 (https://download.01.org/0day-ci/archive/20250923/202509231550.BWhLcP9e-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250923/202509231550.BWhLcP9e-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/202509231550.BWhLcP9e-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/trace/bpf_trace.c:833:41: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __user *[addressable] [assigned] [usertype] sival_ptr @@ got void * @@
kernel/trace/bpf_trace.c:833:41: sparse: expected void [noderef] __user *[addressable] [assigned] [usertype] sival_ptr
kernel/trace/bpf_trace.c:833:41: sparse: got void *
>> kernel/trace/bpf_trace.c:3059:62: sparse: sparse: dubious: x | !y
kernel/trace/bpf_trace.c:3512:52: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3526:56: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3540:52: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3547:56: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3555:52: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3563:56: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c: note: in included file (through include/linux/rbtree.h, include/linux/mm_types.h, include/linux/mmzone.h, ...):
include/linux/rcupdate.h:869:9: sparse: sparse: context imbalance in 'uprobe_prog_run' - unexpected unlock
vim +3059 kernel/trace/bpf_trace.c
3050
3051 static int uprobe_prog_run(struct bpf_uprobe *uprobe,
3052 unsigned long entry_ip,
3053 struct pt_regs *regs,
3054 bool is_return, void *data)
3055 {
3056 struct bpf_uprobe_multi_link *link = uprobe->link;
3057 struct bpf_uprobe_multi_run_ctx run_ctx = {
3058 .session_ctx = {
> 3059 .data = (void *)((unsigned long)data | !!is_return),
3060 },
3061 .entry_ip = entry_ip,
3062 .uprobe = uprobe,
3063 };
3064 struct bpf_prog *prog = link->link.prog;
3065 bool sleepable = prog->sleepable;
3066 struct bpf_run_ctx *old_run_ctx;
3067 int err;
3068
3069 if (link->task && !same_thread_group(current, link->task))
3070 return 0;
3071
3072 if (sleepable)
3073 rcu_read_lock_trace();
3074 else
3075 rcu_read_lock();
3076
3077 migrate_disable();
3078
3079 old_run_ctx = bpf_set_run_ctx(&run_ctx.session_ctx.run_ctx);
3080 err = bpf_prog_run(link->link.prog, regs);
3081 bpf_reset_run_ctx(old_run_ctx);
3082
3083 migrate_enable();
3084
3085 if (sleepable)
3086 rcu_read_unlock_trace();
3087 else
3088 rcu_read_unlock();
3089 return err;
3090 }
3091
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-23 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 9:57 Menglong Dong
2025-09-22 14:08 ` Song Liu
2025-09-22 14:10 ` Menglong Dong
2025-09-23 19:23 ` Alexei Starovoitov
2025-09-24 2:03 ` menglong.dong
2025-09-23 7:52 ` kernel test robot [this message]
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=202509231550.BWhLcP9e-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mattbobrowski@google.com \
--cc=menglong8.dong@gmail.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@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 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®