From: Eugene Korenevsky <ekorenevsky@aliyun.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: nvme_identify_ns_descs: prevent oob
Date: Sat, 29 Nov 2025 22:57:22 +0300 [thread overview]
Message-ID: <aStQImuBjWph8Ywd@localhost.localdomain> (raw)
In-Reply-To: <20251127144916.GA9423@lst.de>
On Thu, Nov 27, 2025 at 03:49:16PM +0100, Christoph Hellwig wrote:
> I think we'll need a somewhat more complex check that at there
> is at least enough space for the len member. But I prefer that
> style over a table lookup and magic name pasting macros.
Okay, simplified the patch. See v2.
next prev parent reply other threads:[~2025-11-29 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 20:27 [PATCH] nvme: nvme_identify_ns_descs: prevent oob Eugene Korenevsky
2025-11-26 20:52 ` Keith Busch
2025-11-26 21:45 ` Eugene Korenevsky
2025-11-27 14:49 ` Christoph Hellwig
2025-11-29 19:57 ` Eugene Korenevsky [this message]
2025-11-30 22:20 ` 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=aStQImuBjWph8Ywd@localhost.localdomain \
--to=ekorenevsky@aliyun.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.