From: Keith Busch <kbusch@kernel.org>
To: <axboe@kernel.dk>, <hch@lst.de>, <sagi@grimberg.me>,
<linux-nvme@lists.infradead.org>, <shao.mingyin@zte.com.cn>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: (subset) [PATCH 0/5] nvme: validate and decode controller supplied values
Date: Fri, 20 Nov 2026 11:54:24 -0800 [thread overview]
Message-ID: <179520446475.200156.12946198917113625003.b4-ty@kernel.org> (raw)
In-Reply-To: <202611150127512368BGQ07ZNIRAIwClkam-8u@zte.com.cn>
On Sun, 15 Nov 2026 01:27:51 +0800 (CST), shao.mingyin@zte.com.cn wrote:
> This series adds missing validation and endian decoding for values that
> come from a controller, a backing controller or a user request.
>
> Patch 1 rejects an invalid ZASL from the controller. nvme_set_max_append()
> shifts 1 by zasl + 3; a value of 29 or more shifts a 32-bit value by 32 or
> more, and the old code also used a signed int for the shift.
>
> [...]
Thanks, applied to nvme-7.4.
[3/5] nvmet: validate the LBA format count of a passthrough namespace
commit: e52b8562e2adb7c3bc77f8899db03f763d9cf49d
[5/5] nvme: bound the reservation report retry loop
commit: b80093c7d0aabb92343f6b333c8ee36e7870ca67
--
Keith Busch <kbusch@kernel.org>
prev parent reply other threads:[~2026-11-20 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 17:27 shao.mingyin
2026-11-14 17:27 ` [PATCH 1/5] nvme: zns: reject an out-of-range zone append size limit shao.mingyin
2026-11-20 17:49 ` Christoph Hellwig
2026-11-22 4:18 ` shao.mingyin
2026-11-14 17:27 ` [PATCH 2/5] nvme: map passthrough data when the length is nonzero shao.mingyin
2026-11-20 17:50 ` Christoph Hellwig
2026-11-20 18:03 ` Caleb Sander Mateos
2026-11-14 17:27 ` [PATCH 3/5] nvmet: validate the LBA format count of a passthrough namespace shao.mingyin
2026-11-20 17:50 ` Christoph Hellwig
2026-11-14 17:27 ` [PATCH 4/5] nvme: decode the FDP Get Features result as a dword shao.mingyin
2026-11-20 17:52 ` Christoph Hellwig
2026-11-14 17:27 ` [PATCH 5/5] nvme: bound the reservation report retry loop shao.mingyin
2026-11-20 17:52 ` Christoph Hellwig
2026-11-20 19:54 ` Keith Busch [this message]
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=179520446475.200156.12946198917113625003.b4-ty@kernel.org \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shao.mingyin@zte.com.cn \
--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
all inboxes | Powered by JetHome®