From: kernel test robot <lkp@intel.com>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, asml.silence@gmail.com,
bpf@vger.kernel.org, axboe@kernel.dk,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH v7 2/5] io_uring/bpf-ops: implement loop_step with BPF struct_ops
Date: Tue, 17 Feb 2026 13:24:03 +0800 [thread overview]
Message-ID: <202602171315.iJKYSSFe-lkp@intel.com> (raw)
In-Reply-To: <ec7d21e6e16c49165fa1e8af2aa09d01c111ea97.1771260487.git.asml.silence@gmail.com>
Hi Pavel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe/for-next]
[also build test WARNING on linus/master next-20260216]
[cannot apply to shuah-kselftest/next shuah-kselftest/fixes v6.19]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Pavel-Begunkov/io_uring-introduce-callback-driven-main-loop/20260217-005705
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/r/ec7d21e6e16c49165fa1e8af2aa09d01c111ea97.1771260487.git.asml.silence%40gmail.com
patch subject: [PATCH v7 2/5] io_uring/bpf-ops: implement loop_step with BPF struct_ops
config: parisc-randconfig-r071-20260217 (https://download.01.org/0day-ci/archive/20260217/202602171315.iJKYSSFe-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
smatch version: v0.5.0-8994-gd50c5a4c
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/202602171315.iJKYSSFe-lkp@intel.com/
smatch warnings:
io_uring/bpf-ops.c:45 bpf_io_btf_struct_access() warn: always true condition '(off >= $expr_0x7fb415932650(30)) => (s32min-s32max >= 0)'
vim +45 io_uring/bpf-ops.c
37
38 static int bpf_io_btf_struct_access(struct bpf_verifier_log *log,
39 const struct bpf_reg_state *reg, int off,
40 int size)
41 {
42 const struct btf_type *t = btf_type_by_id(reg->btf, reg->btf_id);
43
44 if (t == loop_params_type) {
> 45 if (off >= offsetof(struct iou_loop_params, cq_wait_idx) &&
46 off + size <= offsetofend(struct iou_loop_params, cq_wait_idx))
47 return SCALAR_VALUE;
48 }
49
50 return -EACCES;
51 }
52
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-17 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:51 [PATCH v7 0/5] BPF controlled io_uring Pavel Begunkov
2026-02-16 16:51 ` [PATCH v7 1/5] io_uring: introduce callback driven main loop Pavel Begunkov
2026-02-16 16:51 ` [PATCH v7 2/5] io_uring/bpf-ops: implement loop_step with BPF struct_ops Pavel Begunkov
2026-02-17 5:24 ` kernel test robot [this message]
2026-02-17 11:05 ` Pavel Begunkov
2026-02-16 16:51 ` [PATCH v7 3/5] io_uring/bpf-ops: add kfunc helpers Pavel Begunkov
2026-02-16 16:51 ` [PATCH v7 4/5] io_uring/bpf-ops: implement bpf ops registration Pavel Begunkov
2026-02-16 16:51 ` [PATCH v7 5/5] selftests/io_uring: add a bpf io_uring selftest Pavel Begunkov
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=202602171315.iJKYSSFe-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=io-uring@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox