From: Pavel Begunkov <[email protected]>
To: Ming Lei <[email protected]>,
[email protected], Jens Axboe <[email protected]>
Subject: Re: [bug] kernel panic when running ublk selftest on next-20250321
Date: Fri, 21 Mar 2025 14:40:49 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <Z9140ceHEytSh-sz@fedora>
On 3/21/25 14:33, Ming Lei wrote:
> Hello,
>
> When running ublk selftest on today's next tree, the following kernel
> panic is triggered immediately:
Jens already stumbled on that one, it's likely because the
cached structure is not zeroed on alloc. I believe the
troubled patch is removed from the tree for now.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-03-21 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 14:33 [bug] kernel panic when running ublk selftest on next-20250321 Ming Lei
2025-03-21 14:40 ` Pavel Begunkov [this message]
2025-03-21 14:40 ` Jens Axboe
2025-03-21 15:03 ` Ming Lei
2025-03-21 15:13 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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