From: kernel test robot <lkp@intel.com>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Maxwell Bland <mbland@motorola.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: arch/arm64/net/bpf_jit_comp.c:121:38: sparse: sparse: incorrect type in assignment (different base types)
Date: Fri, 19 Dec 2025 16:32:36 +0800 [thread overview]
Message-ID: <202512191616.mTJdtOrm-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dd9b004b7ff3289fb7bae35130c0a5c0537266af
commit: 710618c760c0a3267221517d78f4cfb65ca7b882 arm64/cfi,bpf: Support kCFI + BPF on arm64
date: 5 months ago
config: arm64-randconfig-r121-20251215 (https://download.01.org/0day-ci/archive/20251219/202512191616.mTJdtOrm-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 1335a05ab8bc8339ce24be3a9da89d8c3f4e0571)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251219/202512191616.mTJdtOrm-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/202512191616.mTJdtOrm-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
arch/arm64/net/bpf_jit_comp.c:3071:32: sparse: sparse: arithmetics on pointers to functions
>> arch/arm64/net/bpf_jit_comp.c:121:38: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] @@ got unsigned int const [usertype] data @@
arch/arm64/net/bpf_jit_comp.c:121:38: sparse: expected restricted __le32 [usertype]
arch/arm64/net/bpf_jit_comp.c:121:38: sparse: got unsigned int const [usertype] data
>> arch/arm64/net/bpf_jit_comp.c:121:38: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] @@ got unsigned int const [usertype] data @@
arch/arm64/net/bpf_jit_comp.c:121:38: sparse: expected restricted __le32 [usertype]
arch/arm64/net/bpf_jit_comp.c:121:38: sparse: got unsigned int const [usertype] data
>> arch/arm64/net/bpf_jit_comp.c:3071:17: sparse: sparse: non size-preserving pointer to integer cast
>> arch/arm64/net/bpf_jit_comp.c:3071:17: sparse: sparse: non size-preserving integer to pointer cast
vim +121 arch/arm64/net/bpf_jit_comp.c
117
118 static inline void emit_u32_data(const u32 data, struct jit_ctx *ctx)
119 {
120 if (ctx->image != NULL && ctx->write)
> 121 ctx->image[ctx->idx] = data;
122
123 ctx->idx++;
124 }
125
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-19 8:33 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=202512191616.mTJdtOrm-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbland@motorola.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=puranjay12@gmail.com \
--cc=samitolvanen@google.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.