[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251103115841.GA16274@lst.de>
Date: Mon, 3 Nov 2025 12:58:41 +0100
From: Christoph Hellwig <hch@....de>
To: Alistair Francis <alistair23@...il.com>
Cc: Christoph Hellwig <hch@....de>, kbusch@...nel.org, axboe@...nel.dk,
sagi@...mberg.me, hare@...e.de, kch@...dia.com,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH 3/3] nvme: Allow reauth from sysfs
On Mon, Nov 03, 2025 at 11:47:23AM +1000, Alistair Francis wrote:
> On Sat, Nov 1, 2025 at 12:05 AM Christoph Hellwig <hch@....de> wrote:
> >
> > On Thu, Oct 30, 2025 at 01:51:14PM +1000, alistair23@...il.com wrote:
> > > From: Alistair Francis <alistair.francis@....com>
> > >
> > > Allow userspace to trigger a reauth (REPLACETLSPSK) from sysfs.
> > > This can be done by writing the queue ID to te sysfs file.
> > >
> > > echo 0 > /sys/devices/virtual/nvme-fabrics/ctl/nvme0/replace_psk
> > >
> > > Note that only QID 0 (admin queue) is supported.
> >
> > Why pass the queue ID then instead of a boolean value?
>
> I liked the explicitness of passing a queue ID instead of a bool and
> it allows supporting more queues in the future if that changes in the
> spec.
>
> I can change it to a bool instead if that's preferred?
I find an "echo 0" for a simple one-shot sysfs file rather confusing.
Given that we're not likely to grow anything else I'd vote against
doing it, but this is no hard NAK if there is consensus to do it
this way by others.
Powered by blists - more mailing lists