From: syzbot <syzbot+d36d5ae81e1b0a53ef58@syzkaller.appspotmail.com>
To: alexei.starovoitov@gmail.com, 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,
kafai.wan@hotmail.com, kafai.wan@linux.dev, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, listout@listout.xyz,
martin.lau@linux.dev, netdev@vger.kernel.org, sdf@fomichev.me,
song@kernel.org, syzkaller-bugs@googlegroups.com,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] general protection fault in print_reg_state
Date: Mon, 29 Sep 2025 11:23:03 -0700 [thread overview]
Message-ID: <68dace87.050a0220.1696c6.001b.GAE@google.com> (raw)
In-Reply-To: <68d26227.a70a0220.1b52b.02a4.GAE@google.com>
syzbot has bisected this issue to:
commit aced132599b3c8884c050218d4c48eef203678f6
Author: Song Liu <song@kernel.org>
Date: Wed Jun 25 16:40:24 2025 +0000
bpf: Add range tracking for BPF_NEG
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13931ae2580000
start commit: bf40f4b87761 Merge tag 'probes-fixes-v6.17-rc7' of git://g..
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=10531ae2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17931ae2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d8792ecb6308d0f
dashboard link: https://syzkaller.appspot.com/bug?extid=d36d5ae81e1b0a53ef58
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16010942580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12caeae2580000
Reported-by: syzbot+d36d5ae81e1b0a53ef58@syzkaller.appspotmail.com
Fixes: aced132599b3 ("bpf: Add range tracking for BPF_NEG")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2025-09-29 18:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <68d26227.a70a0220.1b52b.02a4.GAE@google.com>]
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=68dace87.050a0220.1696c6.001b.GAE@google.com \
--to=syzbot+d36d5ae81e1b0a53ef58@syzkaller.appspotmail.com \
--cc=alexei.starovoitov@gmail.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=kafai.wan@hotmail.com \
--cc=kafai.wan@linux.dev \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=listout@listout.xyz \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--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).