From: syzbot <syzbot+ccac90e482b2a81d74aa@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,
paul.chaignon@gmail.com, sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in convert_ctx_accesses
Date: Thu, 31 Jul 2025 06:43:05 -0700 [thread overview]
Message-ID: <688b72e9.050a0220.5d226.0018.GAE@google.com> (raw)
In-Reply-To: <688ae0bf.050a0220.5d226.0011.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=17d6aca2580000
start commit: e8d780dcd957 Merge tag 'slab-for-6.17' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1436aca2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1036aca2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d32de89be62206c8
dashboard link: https://syzkaller.appspot.com/bug?extid=ccac90e482b2a81d74aa
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=131049bc580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11cc2cf0580000
Reported-by: syzbot+ccac90e482b2a81d74aa@syzkaller.appspotmail.com
Fixes: 0df1a55afa83 ("bpf: Warn on internal verifier errors")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-07-31 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 3:19 [syzbot] [bpf?] WARNING in convert_ctx_accesses syzbot
2025-07-31 13:43 ` syzbot [this message]
2025-07-31 13:53 ` 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=688b72e9.050a0220.5d226.0018.GAE@google.com \
--to=syzbot+ccac90e482b2a81d74aa@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=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 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.