From: Jens Axboe <axboe@kernel.dk>
To: Longxing Li <coregee2000@gmail.com>,
syzkaller@googlegroups.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Kernel Bug] INFO: rcu detected stall in disk_check_events
Date: Tue, 9 Jun 2026 06:41:49 -0600 [thread overview]
Message-ID: <8b2f0830-23cf-4f6f-89a4-1390cb0f2e88@kernel.dk> (raw)
In-Reply-To: <CAHPqNmzE6bcNb3T+nJavn-mg=w2B0F1YCv47qv-Tsbn4xOrGmw@mail.gmail.com>
On 6/9/26 5:52 AM, Longxing Li wrote:
> Dear Linux kernel developers and maintainers,
>
> We would like to report a new kernel bug found by our tool. INFO: rcu
> detected stall in disk_check_events. Details are as follows.
>
> Kernel commit: v7.0.6
> Kernel config: see attachment
> report: see attachment
>
> We are currently analyzing the root cause and working on a
> reproducible PoC. We will provide further updates in this thread as
> soon as we have more information.
Please include pertinent information in the email rather than some
shared drive somewhere.
--
Jens Axboe
next prev parent reply other threads:[~2026-06-09 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 11:52 [Kernel Bug] INFO: rcu detected stall in disk_check_events Longxing Li
2026-06-09 12:41 ` Jens Axboe [this message]
2026-06-10 7:05 ` Longxing Li
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=8b2f0830-23cf-4f6f-89a4-1390cb0f2e88@kernel.dk \
--to=axboe@kernel.dk \
--cc=coregee2000@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox