From: Christoph Hellwig <hch@lst.de>
To: alan.adamson@oracle.com
Cc: Yi Zhang <yi.zhang@redhat.com>,
linux-block <linux-block@vger.kernel.org>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
Christoph Hellwig <hch@lst.de>,
John Garry <john.g.garry@oracle.com>
Subject: Re: [bug report] nvme4: inconsistent AWUPF, controller not added (0/7).
Date: Thu, 3 Jul 2025 10:03:59 +0200 [thread overview]
Message-ID: <20250703080359.GA365@lst.de> (raw)
In-Reply-To: <6e74e9a8-2dbb-4ad4-a48b-9af40d6af711@oracle.com>
On Wed, Jul 02, 2025 at 09:33:32AM -0700, alan.adamson@oracle.com wrote:
> Looks like the device isn't reporting AWUPF after the format/reset.
The other option would be that the format changed the value.
The mess NVMe creasted with the totally un-thought out atomics is
beyond belive :(
I wonder if we should just back out the whole thing and wait for the
working group to come up with something that can actually safely work.
next prev parent reply other threads:[~2025-07-03 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 11:13 [bug report] nvme4: inconsistent AWUPF, controller not added (0/7) Yi Zhang
2025-07-02 16:33 ` alan.adamson
2025-07-03 8:03 ` Christoph Hellwig [this message]
2025-07-03 17:47 ` Yi Zhang
2025-07-04 2:17 ` Ming Lei
2025-07-07 5:37 ` Christoph Hellwig
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=20250703080359.GA365@lst.de \
--to=hch@lst.de \
--cc=alan.adamson@oracle.com \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=yi.zhang@redhat.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