From: syzbot <syzbot+69014a227f8edad4d8c6@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, paul.chaignon@gmail.com,
sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in check_helper_call
Date: Wed, 02 Jul 2025 15:04:03 -0700 [thread overview]
Message-ID: <6865acd3.a70a0220.2b31f5.0005.GAE@google.com> (raw)
In-Reply-To: <686491d6.a70a0220.3b7e22.20ea.GAE@google.com>
syzbot has bisected this issue to:
commit 0df1a55afa832f463f9ad68ddc5de92230f1bc8a
Author: Paul Chaignon <paul.chaignon@gmail.com>
Date: Tue Jul 1 18:36:15 2025 +0000
bpf: Warn on internal verifier errors
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155a848c580000
start commit: cce3fee729ee selftests/bpf: Enable dynptr/test_probe_read_..
git tree: bpf-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=175a848c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=135a848c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=79da270cec5ffd65
dashboard link: https://syzkaller.appspot.com/bug?extid=69014a227f8edad4d8c6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144053d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d45770580000
Reported-by: syzbot+69014a227f8edad4d8c6@syzkaller.appspotmail.com
Fixes: 0df1a55afa83 ("bpf: Warn on internal verifier errors")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-07-02 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 1:56 [syzbot] [bpf?] WARNING in check_helper_call syzbot
2025-07-02 22:04 ` 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=6865acd3.a70a0220.2b31f5.0005.GAE@google.com \
--to=syzbot+69014a227f8edad4d8c6@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=paul.chaignon@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;
as well as URLs for NNTP newsgroup(s).