From: syzbot <syzbot+e1fa4a4a9361f2f3bbd6@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, luis.gerhorst@fau.de,
martin.lau@linux.dev, sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in do_check (2)
Date: Mon, 15 Sep 2025 20:50:03 -0700 [thread overview]
Message-ID: <68c8de6b.050a0220.3c6139.0d26.GAE@google.com> (raw)
In-Reply-To: <68c85b0d.050a0220.2ff435.03a5.GAE@google.com>
syzbot has bisected this issue to:
commit dadb59104c6441f54d0c42bba3e4bd11e25fc6d9
Author: Luis Gerhorst <luis.gerhorst@fau.de>
Date: Sat Jul 5 19:09:07 2025 +0000
bpf: Fix aux usage after do_check_insn()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13850534580000
start commit: f83ec76bf285 Linux 6.17-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10450534580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17850534580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d8792ecb6308d0f
dashboard link: https://syzkaller.appspot.com/bug?extid=e1fa4a4a9361f2f3bbd6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1355f934580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12170e42580000
Reported-by: syzbot+e1fa4a4a9361f2f3bbd6@syzkaller.appspotmail.com
Fixes: dadb59104c64 ("bpf: Fix aux usage after do_check_insn()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-16 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 18:29 [syzbot] [bpf?] WARNING in do_check (2) syzbot
2025-09-16 3:50 ` syzbot [this message]
2025-09-19 14:20 ` Paul Chaignon
2025-09-19 15:13 ` syzbot
2025-09-22 11:17 ` Paul Chaignon
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=68c8de6b.050a0220.3c6139.0d26.GAE@google.com \
--to=syzbot+e1fa4a4a9361f2f3bbd6@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=luis.gerhorst@fau.de \
--cc=martin.lau@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.