From: Greg KH <gregkh@linuxfoundation.org>
To: Hagar Hemdan <hagarhem@amazon.com>
Cc: stable@vger.kernel.org, Puranjay Mohan <pjy@amazon.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Anuj Gupta <anuj20.g@samsung.com>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 6.1] nvme: fix metadata handling in nvme-passthrough
Date: Tue, 4 Feb 2025 14:56:08 +0100 [thread overview]
Message-ID: <2025020400-henna-diocese-80c7@gregkh> (raw)
In-Reply-To: <20250203082501.28771-1-hagarhem@amazon.com>
On Mon, Feb 03, 2025 at 08:24:58AM +0000, Hagar Hemdan wrote:
> From: Puranjay Mohan <pjy@amazon.com>
>
> [ Upstream commit 7c2fd76048e95dd267055b5f5e0a48e6e7c81fd9 ]
>
> On an NVMe namespace that does not support metadata, it is possible to
> send an IO command with metadata through io-passthru. This allows issues
> like [1] to trigger in the completion code path.
> nvme_map_user_request() doesn't check if the namespace supports metadata
> before sending it forward. It also allows admin commands with metadata to
> be processed as it ignores metadata when bdev == NULL and may report
> success.
>
> Reject an IO command with metadata when the NVMe namespace doesn't
> support it and reject an admin command if it has metadata.
>
> [1] https://lore.kernel.org/all/mb61pcylvnym8.fsf@amazon.com/
>
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
> Reviewed-by: Anuj Gupta <anuj20.g@samsung.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> [ Minor changes to make it work on 6.1 ]
> Signed-off-by: Puranjay Mohan <pjy@amazon.com>
> Signed-off-by: Hagar Hemdan <hagarhem@amazon.com>
> ---
> Resend as all stables contain the fix except 6.1.
Good catch, thanks!
greg k-h
next prev parent reply other threads:[~2025-02-04 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 8:24 [PATCH 6.1] nvme: fix metadata handling in nvme-passthrough Hagar Hemdan
2025-02-03 12:37 ` Sasha Levin
2025-02-04 13:56 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-25 12:10 [PATCH 6.6] " Hagar Hemdan
2024-11-25 12:10 ` [PATCH 6.1] " Hagar Hemdan
2024-11-25 15:20 ` Sasha Levin
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=2025020400-henna-diocese-80c7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anuj20.g@samsung.com \
--cc=hagarhem@amazon.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=pjy@amazon.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
/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