From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "alistair23@gmail.com" <alistair23@gmail.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"hare@suse.de" <hare@suse.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v2 4/4] nvme: Allow reauth from sysfs
Date: Wed, 12 Nov 2025 00:45:03 +0000 [thread overview]
Message-ID: <69f44147-3c9e-41b5-9b26-5e235a418f6c@nvidia.com> (raw)
In-Reply-To: <20251111234519.3467440-5-alistair.francis@wdc.com>
On 11/11/25 3:45 PM, alistair23@gmail.com wrote:
> From: Alistair Francis<alistair.francis@wdc.com>
>
> Allow userspace to trigger a reauth (REPLACETLSPSK) from sysfs.
> This can be done by writing to the sysfs file.
>
> echo 0 > /sys/devices/virtual/nvme-fabrics/ctl/nvme0/tls_configured_key
>
> Signed-off-by: Alistair Francis<alistair.francis@wdc.com>
LGTM,
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> -ck
next prev parent reply other threads:[~2025-11-12 0:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 23:45 [PATCH v2 0/4] Support PSK reauthentication (REPLACETLSPSK) alistair23
2025-11-11 23:45 ` [PATCH v2 1/4] nvmet-tcp: Don't error if TLS is enabed on a reset alistair23
2025-11-12 1:13 ` Wilfred Mallawa
2025-11-12 6:54 ` Christoph Hellwig
2025-11-12 7:05 ` Hannes Reinecke
2025-11-11 23:45 ` [PATCH v2 2/4] nvmet-tcp: Don't free SQ on authentication success alistair23
2025-11-12 6:54 ` Christoph Hellwig
2025-11-12 7:07 ` Hannes Reinecke
2025-11-11 23:45 ` [PATCH v2 3/4] nvme: Expose the tls_configured sysfs for secure concat connections alistair23
2025-11-12 6:54 ` Christoph Hellwig
2025-11-12 7:08 ` Hannes Reinecke
2025-11-13 2:08 ` Alistair Francis
2025-11-13 7:21 ` Hannes Reinecke
2025-11-13 12:22 ` Alistair Francis
2025-11-13 12:45 ` Hannes Reinecke
2025-11-14 3:47 ` Alistair Francis
2025-11-11 23:45 ` [PATCH v2 4/4] nvme: Allow reauth from sysfs alistair23
2025-11-12 0:45 ` Chaitanya Kulkarni [this message]
2025-11-12 6:56 ` Christoph Hellwig
2025-11-13 12:23 ` Alistair Francis
2025-11-12 7:12 ` Hannes Reinecke
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=69f44147-3c9e-41b5-9b26-5e235a418f6c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox