From: Wilfred Mallawa <wilfred.opensource@gmail.com>
To: alistair23@gmail.com, kbusch@kernel.org, axboe@kernel.dk,
hch@lst.de, sagi@grimberg.me, hare@suse.de, kch@nvidia.com,
linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v4 4/4] nvme: Allow reauth from sysfs
Date: Sat, 13 Dec 2025 12:33:16 +0900 [thread overview]
Message-ID: <101bb8011cc6be8e60409d294c8c0abe93b9ed72.camel@gmail.com> (raw)
In-Reply-To: <20251202051755.1312158-5-alistair.francis@wdc.com>
On Tue, 2025-12-02 at 15:17 +1000, 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 a zero to the sysfs file.
>
> echo 0 > /sys/devices/virtual/nvme-
> fabrics/ctl/nvme0/tls_configured_key
>
> In order to use the new keys for the admin queue we call controller
> reset. This isn't ideal, but I can't find a simpler way to reset the
> admin queue TLS connection.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> ---
> v4:
> - Forcefully reset the connection
> v3:
> - Only trigger if a 0 is written to `tls_configured_key`
> - Add documentation
> v2:
> - Trigger on any value written to `tls_configured_key`
>
> Documentation/ABI/testing/sysfs-nvme | 13 ++++++++
> drivers/nvme/host/sysfs.c | 44
> +++++++++++++++++++++++++++-
> 2 files changed, 56 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/ABI/testing/sysfs-nvme
>
> diff --git a/Documentation/ABI/testing/sysfs-nvme
> b/Documentation/ABI/testing/sysfs-nvme
> new file mode 100644
> index 000000000000..16aaf0dca9e2
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-nvme
> @@ -0,0 +1,13 @@
> +What: /sys/devices/virtual/nvme-
> fabrics/ctl/.../tls_configured_key
> +Date: November 2025
> +KernelVersion: 6.19
> +Contact: Linux NVMe mailing list
> <linux-nvme@lists.infradead.org>
> +Description:
> + The file is avaliable when using a secure
> concatanation
> + connection to a NVMe taget. Reading the file will
> returns
s/a NVMe taget/an NVMe target
s/returns/return
Otherwise LGTM
Reviewed-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
Wilfred
next prev parent reply other threads:[~2025-12-13 3:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 5:17 [PATCH v4 0/4] Support PSK reauthentication (REPLACETLSPSK) alistair23
2025-12-02 5:17 ` [PATCH v4 1/4] nvmet-tcp: Don't error if TLS is enabed on a reset alistair23
2025-12-12 13:48 ` Sagi Grimberg
2025-12-02 5:17 ` [PATCH v4 2/4] nvmet-tcp: Don't free SQ on authentication success alistair23
2025-12-12 13:49 ` Sagi Grimberg
2025-12-02 5:17 ` [PATCH v4 3/4] nvme: Expose the tls_configured sysfs for secure concat connections alistair23
2025-12-12 13:50 ` Sagi Grimberg
2025-12-02 5:17 ` [PATCH v4 4/4] nvme: Allow reauth from sysfs alistair23
2025-12-02 6:03 ` Christoph Hellwig
2025-12-02 15:30 ` Hannes Reinecke
2025-12-12 13:52 ` Sagi Grimberg
2025-12-13 3:33 ` Wilfred Mallawa [this message]
2026-03-02 3:42 ` [PATCH v4 0/4] Support PSK reauthentication (REPLACETLSPSK) Alistair Francis
2026-03-02 20:09 ` Keith Busch
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=101bb8011cc6be8e60409d294c8c0abe93b9ed72.camel@gmail.com \
--to=wilfred.opensource@gmail.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=kch@nvidia.com \
--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