From: syzbot <syzbot+ba82760c63ba37799f70@syzkaller.appspotmail.com>
To: andrii@kernel.org, aou@eecs.berkeley.edu, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, martin.lau@linux.dev,
netdev@vger.kernel.org, olsajiri@gmail.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, puranjay12@gmail.com, sdf@google.com,
song@kernel.org, syzkaller-bugs@googlegroups.com,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] general protection fault in bpf_check (2)
Date: Thu, 30 May 2024 20:41:04 -0700 [thread overview]
Message-ID: <000000000000cf8dba0619b7c0db@google.com> (raw)
In-Reply-To: <0000000000007628d60614449e5d@google.com>
syzbot suspects this issue was fixed by commit:
commit 122fdbd2a030a95128737fc77e47df15a8f170c3
Author: Puranjay Mohan <puranjay12@gmail.com>
Date: Fri Mar 22 15:35:18 2024 +0000
bpf: verifier: reject addr_space_cast insn without arena
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e17d3c980000
start commit: 4c2a26fc80bc bpf-next: Avoid goto in regs_refine_cond_op()
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=ba82760c63ba37799f70
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e6bbb9180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12941291180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: verifier: reject addr_space_cast insn without arena
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-05-31 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 19:13 [syzbot] [bpf?] general protection fault in bpf_check (2) syzbot
2024-03-22 21:44 ` Jiri Olsa
2024-03-24 8:37 ` syzbot
2024-05-31 3:41 ` syzbot [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=000000000000cf8dba0619b7c0db@google.com \
--to=syzbot+ba82760c63ba37799f70@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=puranjay12@gmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--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;
as well as URLs for NNTP newsgroup(s).