Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Aithal, Srikanth" <sraithal@amd.com>
To: Christoph Hellwig <hch@lst.de>, hare@kernel.org
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: fixup boot failure on nvme-pci
Date: Mon, 14 Apr 2025 18:37:47 +0530	[thread overview]
Message-ID: <4287dbe2-c695-4e04-8413-79797ad19ea9@amd.com> (raw)
In-Reply-To: <20250414122616.GA14884@lst.de>


On 4/14/2025 5:56 PM, Christoph Hellwig wrote:
> On Mon, Apr 14, 2025 at 02:05:09PM +0200, hare@kernel.org wrote:
>> From: Hannes Reinecke <hare@kernel.org>
>>
>> Commit 62baf70c3274 caused the ANA log page to be re-read, even on systems
>> where the ANA is not supported.
> And unsupported log page should normally not cause a boot failure, but
> it seems the controller in question does not handle it well.  I've
> applied the patch with a better subjet and commit message explaining this.
>
> But if the controller handles unsupported log pages so badly it will
> probably cause trouble in the future as well, or even now when
> applications ask for unsupported log pages using the passthrough
> interfaces.
>
> Srikanth: what controller is this?  I'd like to add that to the commit
> message as well.

It is a Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe 
SSD Controller SM981/PM981/PM983


>


  reply	other threads:[~2025-04-14 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 12:05 [PATCH] nvme: fixup boot failure on nvme-pci hare
2025-04-14 12:26 ` Christoph Hellwig
2025-04-14 13:07   ` Aithal, Srikanth [this message]
2025-04-14 14:23   ` Domenico Andreoli
2025-04-16  6:48   ` Aithal, Srikanth
2025-04-16 14:29     ` Keith Busch
2025-04-14 22:09 ` Sagi Grimberg

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=4287dbe2-c695-4e04-8413-79797ad19ea9@amd.com \
    --to=sraithal@amd.com \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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