From: syzbot <syzbot+3afc814e8df1af64b653@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
henriette.herzog@rub.de, john.fastabend@gmail.com,
jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, luis.gerhorst@fau.de,
martin.lau@linux.dev, memxor@gmail.com, sdf@fomichev.me,
song@kernel.org, syzkaller-bugs@googlegroups.com,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in maybe_exit_scc
Date: Tue, 16 Sep 2025 03:20:03 -0700 [thread overview]
Message-ID: <68c939d3.050a0220.2ff435.03c1.GAE@google.com> (raw)
In-Reply-To: <68c85acd.050a0220.2ff435.03a4.GAE@google.com>
syzbot has bisected this issue to:
commit d6f1c85f22534d2d9fea9b32645da19c91ebe7d2
Author: Luis Gerhorst <luis.gerhorst@fau.de>
Date: Tue Jun 3 21:24:28 2025 +0000
bpf: Fall back to nospec for Spectre v1
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17753762580000
start commit: f83ec76bf285 Linux 6.17-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f53762580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f53762580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f01d8629880e620
dashboard link: https://syzkaller.appspot.com/bug?extid=3afc814e8df1af64b653
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104a947c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14467b62580000
Reported-by: syzbot+3afc814e8df1af64b653@syzkaller.appspotmail.com
Fixes: d6f1c85f2253 ("bpf: Fall back to nospec for Spectre v1")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-16 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 18:28 [syzbot] [bpf?] WARNING in maybe_exit_scc syzbot
2025-09-15 22:34 ` Eduard Zingerman
2025-09-15 23:40 ` Eduard Zingerman
2025-09-16 9:14 ` Eduard Zingerman
2025-09-16 10:20 ` syzbot [this message]
2025-09-29 7:57 ` Luis Gerhorst
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=68c939d3.050a0220.2ff435.03c1.GAE@google.com \
--to=syzbot+3afc814e8df1af64b653@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=henriette.herzog@rub.de \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--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