From: Keith Busch <kbusch@kernel.org>
To: Hannes Reinecke <hare@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCHv5] nvmet: implement unique discovery NQN
Date: Thu, 4 Apr 2024 09:58:52 -0600 [thread overview]
Message-ID: <Zg7OPNrrFSxMCnMR@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20240403113114.76342-1-hare@kernel.org>
On Wed, Apr 03, 2024 at 01:31:14PM +0200, Hannes Reinecke wrote:
> Unique discovery NQNs allow to differentiate between discovery
> services from (typically physically separate) NVMe-oF subsystems.
> This is required for establishing secured connections as otherwise
> the credentials won't be unique and the integrity of the connection
> cannot be guaranteed.
> This patch adds a configfs attribute 'discovery_nqn' in the 'nvmet'
> configfs directory to specify the unique discovery NQN.
Thanks, applied to nvme-6.9.
prev parent reply other threads:[~2024-04-04 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 11:31 [PATCHv5] nvmet: implement unique discovery NQN Hannes Reinecke
2024-04-03 22:17 ` Chaitanya Kulkarni
2024-04-04 15:58 ` 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=Zg7OPNrrFSxMCnMR@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).