From: syzbot <syzbot+fa5c2814795b5adca240@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, hffilwlqm@gmail.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
memxor@gmail.com, netdev@vger.kernel.org, sdf@fomichev.me,
song@kernel.org, syzkaller-bugs@googlegroups.com,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] possible deadlock in __bpf_ringbuf_reserve (2)
Date: Mon, 01 Sep 2025 15:10:04 -0700 [thread overview]
Message-ID: <68b619bc.050a0220.3db4df.01c5.GAE@google.com> (raw)
In-Reply-To: <68ac9fd3.050a0220.37038e.0096.GAE@google.com>
syzbot has bisected this issue to:
commit 27861fc720be2c39b861d8bdfb68287f54de6855
Author: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Date: Thu Aug 21 16:26:00 2025 +0000
bpf: Drop rqspinlock usage in ringbuf
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=167eee34580000
start commit: dd9de524183a xsk: Fix immature cq descriptor production
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=157eee34580000
console output: https://syzkaller.appspot.com/x/log.txt?x=117eee34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c321f33e4545e2a1
dashboard link: https://syzkaller.appspot.com/bug?extid=fa5c2814795b5adca240
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142da862580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1588aef0580000
Reported-by: syzbot+fa5c2814795b5adca240@syzkaller.appspotmail.com
Fixes: 27861fc720be ("bpf: Drop rqspinlock usage in ringbuf")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-01 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 17:39 [syzbot] [bpf?] possible deadlock in __bpf_ringbuf_reserve (2) syzbot
2025-08-26 2:20 ` Leon Hwang
2025-08-26 2:23 ` Alexei Starovoitov
2025-08-26 2:30 ` Leon Hwang
2025-09-01 22:10 ` 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=68b619bc.050a0220.3db4df.01c5.GAE@google.com \
--to=syzbot+fa5c2814795b5adca240@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=hffilwlqm@gmail.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=memxor@gmail.com \
--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).