From: Eduard Zingerman <eddyz87@gmail.com>
To: Liu RuiTong <cnitlrt@gmail.com>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: KASAN: null-ptr-deref in bpf_core_calc_relo_insn
Date: Tue, 20 Aug 2024 18:33:11 -0700 [thread overview]
Message-ID: <badd583d09868ffdd48a97c727680ca6f5699727.camel@gmail.com> (raw)
In-Reply-To: <CAK55_s6do7C+DVwbwY_7nKfUz0YLDoiA1v6X3Y9+p0sWzipFSA@mail.gmail.com>
On Tue, 2024-08-20 at 17:21 +0800, Liu RuiTong wrote:
[...]
> bpf_core_calc_relo_insn+311 <bpf_core_calc_relo_insn+311>
> ─────────────────────────────────────────────────────────────────────────────────────────────[
> SOURCE (CODE) ]──────────────────────────────────────────────────────────────────────────────────────────────
> In file: /home/ubuntu/fuzz/linux-6.11-rc4/tools/lib/bpf/relo_core.c:1300
> 1295 char spec_buf[256];
> 1296 int i, j, err;
> 1297
> 1298 local_id = relo->type_id;
> 1299 local_type = btf_type_by_id(local_btf, local_id);
> ► 1300 local_name = btf__name_by_offset(local_btf,
> local_type->name_off);
Hi Liu,
Thank you for the report, I can reproduce the issue.
Will comment later today.
> 1301 if (!local_name)
> 1302 return -EINVAL;
> 1303
> 1304 err = bpf_core_parse_spec(prog_name, local_btf, relo,
> local_spec);
> 1305 if (err) {
> ─────────────────────────────────────────────────────────────────────────────────────────────────[
> STACK ]──────────────────────────────────────────────────────────────────────────────────────────────────
> ```
next prev parent reply other threads:[~2024-08-21 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 9:21 KASAN: null-ptr-deref in bpf_core_calc_relo_insn Liu RuiTong
2024-08-21 1:33 ` Eduard Zingerman [this message]
2024-08-21 11:46 ` Eduard Zingerman
2024-08-21 16:04 ` Eduard Zingerman
2024-08-21 16:40 ` Alexei Starovoitov
2024-08-21 16:42 ` Eduard Zingerman
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=badd583d09868ffdd48a97c727680ca6f5699727.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cnitlrt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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