From: kernel test robot <lkp@intel.com>
To: Mykyta Yatsenko <yatsenko@meta.com>
Cc: oe-kbuild-all@lists.linux.dev,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Subject: [bpf-next:master 2/4] kernel/trace/bpf_trace.c:3619:52: sparse: sparse: cast removes address space '__user' of expression
Date: Fri, 16 May 2025 04:15:12 +0800 [thread overview]
Message-ID: <202505160426.4odfmpXg-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
head: 9325d53fe9adff354b6a93fda5f38c165947da0f
commit: a498ee7576de24b4b0916ce56cf2686e261a29f7 [2/4] bpf: Implement dynptr copy kfuncs
config: x86_64-randconfig-123-20250515 (https://download.01.org/0day-ci/archive/20250516/202505160426.4odfmpXg-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250516/202505160426.4odfmpXg-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/202505160426.4odfmpXg-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/trace/bpf_trace.c:835: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:835:41: sparse: expected void [noderef] __user *[addressable] [assigned] [usertype] sival_ptr
kernel/trace/bpf_trace.c:835:41: sparse: got void *
>> kernel/trace/bpf_trace.c:3619:52: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3633:56: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3647:52: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3654:56: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3662:52: sparse: sparse: cast removes address space '__user' of expression
kernel/trace/bpf_trace.c:3670: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:871:25: sparse: sparse: context imbalance in 'uprobe_prog_run' - unexpected unlock
vim +/__user +3619 kernel/trace/bpf_trace.c
3615
3616 __bpf_kfunc int bpf_probe_read_user_dynptr(struct bpf_dynptr *dptr, u32 off,
3617 u32 size, const void __user *unsafe_ptr__ign)
3618 {
> 3619 return __bpf_dynptr_copy(dptr, off, size, (const void *)unsafe_ptr__ign,
3620 copy_user_data_nofault, NULL);
3621 }
3622
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-15 20:15 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=202505160426.4odfmpXg-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yatsenko@meta.com \
/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.