From: Christoph Hellwig <hch@lst.de>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
dlemoal@kernel.org, kbusch@kernel.org, kch@nvidia.com,
sagi@grimberg.me, hch@lst.de, upstream+nvme@sigma-star.at
Subject: Re: [PATCH] nvmet: Fix out-of-bounds access in nvmet_enable_port
Date: Tue, 22 Apr 2025 09:50:53 +0200 [thread overview]
Message-ID: <20250422075053.GA32269@lst.de> (raw)
In-Reply-To: <20250418080250.2736590-1-richard@nod.at>
Thanks,
applied to nvme-6.15.
prev parent reply other threads:[~2025-04-22 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 8:02 [PATCH] nvmet: Fix out-of-bounds access in nvmet_enable_port Richard Weinberger
2025-04-18 8:04 ` Damien Le Moal
2025-04-18 10:54 ` Sagi Grimberg
2025-04-22 6:33 ` Chaitanya Kulkarni
2025-04-22 7:50 ` Christoph Hellwig [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=20250422075053.GA32269@lst.de \
--to=hch@lst.de \
--cc=dlemoal@kernel.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=richard@nod.at \
--cc=sagi@grimberg.me \
--cc=upstream+nvme@sigma-star.at \
/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