From: Eduard Zingerman <eddyz87@gmail.com>
To: Nuiqi Gui <gnq25@mails.tsinghua.edu.cn>,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org
Cc: dxu@dxuuu.xyz, Martin KaFai Lau <martin.lau@linux.dev>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Ihor Solodrai <isolodrai@meta.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf 2/2] selftests/bpf: Cover dynamic inner array lookup nullability
Date: Fri, 05 Jun 2026 02:48:05 -0700 [thread overview]
Message-ID: <70d13621ffcc36e3254ab78f8f1cf14c4c9b4f03.camel@gmail.com> (raw)
In-Reply-To: <20260604151153.2488051-3-gnq25@mails.tsinghua.edu.cn>
On Thu, 2026-06-04 at 23:11 +0800, Nuiqi Gui wrote:
> Add a verifier regression test that looks up a constant key through a
> dynamic inner array template and dereferences the result without a NULL
> check.
>
> The verifier must reject the program because BPF_F_INNER_MAP allows the
> concrete runtime array to have fewer entries than the template.
>
> Signed-off-by: Nuiqi Gui <gnq25@mails.tsinghua.edu.cn>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
prev parent reply other threads:[~2026-06-05 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260604151153.2488051-1-gnq25@mails.tsinghua.edu.cn>
2026-06-04 15:11 ` [PATCH bpf 1/2] bpf: Keep dynamic inner array lookups nullable Nuiqi Gui
2026-06-04 18:13 ` Magneto
2026-06-04 18:35 ` Suchit Karunakaran
2026-06-05 9:47 ` Eduard Zingerman
2026-06-04 15:11 ` [PATCH bpf 2/2] selftests/bpf: Cover dynamic inner array lookup nullability Nuiqi Gui
2026-06-05 9:48 ` Eduard Zingerman [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=70d13621ffcc36e3254ab78f8f1cf14c4c9b4f03.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=gnq25@mails.tsinghua.edu.cn \
--cc=isolodrai@meta.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--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
Powered by JetHome