From: syzbot <syzbot+cbc79a37b5fa23efd23b@syzkaller.appspotmail.com>
To: agordeev@linux.ibm.com, boqun.feng@gmail.com,
guoweikang.kernel@gmail.com, hdanton@sina.com,
kent.overstreet@linux.dev, kpsingh@kernel.org,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
paulmck@kernel.org, pmladek@suse.com, rppt@kernel.org,
rrangel@chromium.org, syzkaller-bugs@googlegroups.com,
urezki@gmail.com
Subject: Re: [syzbot] [bcachefs?] possible deadlock in start_poll_synchronize_rcu_expedited
Date: Mon, 02 Jun 2025 06:02:02 -0700 [thread overview]
Message-ID: <683da0ca.a00a0220.d8eae.0051.GAE@google.com> (raw)
In-Reply-To: <683447f8.a70a0220.29d4a0.0803.GAE@google.com>
syzbot has bisected this issue to:
commit 82067c916994dd1bfec65496144dc16e17899e36
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri May 9 03:21:28 2025 +0000
bcachefs: buckets_in_flight on stack
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12fc7970580000
start commit: 3a83b350b5be Add linux-next specific files for 20250530
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11fc7970580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16fc7970580000
kernel config: https://syzkaller.appspot.com/x/.config?x=28859360c84ac63d
dashboard link: https://syzkaller.appspot.com/bug?extid=cbc79a37b5fa23efd23b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=106ebed4580000
Reported-by: syzbot+cbc79a37b5fa23efd23b@syzkaller.appspotmail.com
Fixes: 82067c916994 ("bcachefs: buckets_in_flight on stack")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-02 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 10:52 [syzbot] [kernel?] possible deadlock in start_poll_synchronize_rcu_expedited syzbot
2025-05-31 22:10 ` [syzbot] [bcachefs?] " syzbot
2025-06-02 13:02 ` syzbot [this message]
[not found] <20250531232348.2486-1-hdanton@sina.com>
2025-05-31 23:42 ` syzbot
[not found] <20250601012256.2510-1-hdanton@sina.com>
2025-06-01 1:59 ` syzbot
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=683da0ca.a00a0220.d8eae.0051.GAE@google.com \
--to=syzbot+cbc79a37b5fa23efd23b@syzkaller.appspotmail.com \
--cc=agordeev@linux.ibm.com \
--cc=boqun.feng@gmail.com \
--cc=guoweikang.kernel@gmail.com \
--cc=hdanton@sina.com \
--cc=kent.overstreet@linux.dev \
--cc=kpsingh@kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rppt@kernel.org \
--cc=rrangel@chromium.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=urezki@gmail.com \
/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.