From: syzbot <syzbot+ba82760c63ba37799f70@syzkaller.appspotmail.com>
To: andrii@kernel.org, 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, martin.lau@linux.dev,
netdev@vger.kernel.org, olsajiri@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: Sun, 24 Mar 2024 01:37:02 -0700 [thread overview]
Message-ID: <000000000000077c22061463f6f5@google.com> (raw)
In-Reply-To: <0000000000007628d60614449e5d@google.com>
syzbot has bisected this issue to:
commit 6082b6c328b5486da2b356eae94b8b83c98b5565
Author: Alexei Starovoitov <ast@kernel.org>
Date: Fri Mar 8 01:08:03 2024 +0000
bpf: Recognize addr_space_cast instruction in the verifier.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101f5ac9180000
start commit: ddb2ffdc474a libbpf: Define MFD_CLOEXEC if not available
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=121f5ac9180000
console output: https://syzkaller.appspot.com/x/log.txt?x=141f5ac9180000
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=115671f1180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f14e31180000
Reported-by: syzbot+ba82760c63ba37799f70@syzkaller.appspotmail.com
Fixes: 6082b6c328b5 ("bpf: Recognize addr_space_cast instruction in the verifier.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-03-24 8:37 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 [this message]
2024-05-31 3:41 ` syzbot
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=000000000000077c22061463f6f5@google.com \
--to=syzbot+ba82760c63ba37799f70@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--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=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@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).