linux-kernel - Re: [RFC PATCH] nvme: add an opt-in to use AWUPF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aKciTPKiL8wRWmHA@kbusch-mbp>
Date: Thu, 21 Aug 2025 07:42:36 -0600
From: Keith Busch <kbusch@...nel.org>
To: Nilay Shroff <nilay@...ux.ibm.com>
Cc: John Garry <john.g.garry@...cle.com>, axboe@...nel.dk, hch@....de,
	sagi@...mberg.me, linux-nvme@...ts.infradead.org,
	linux-kernel@...r.kernel.org, tytso@....edu,
	martin.petersen@...cle.com, djwong@...nel.org, mcgrof@...radead.org
Subject: Re: [RFC PATCH] nvme: add an opt-in to use AWUPF

On Thu, Aug 21, 2025 at 10:55:31AM +0530, Nilay Shroff wrote:
> On 8/21/25 3:21 AM, Keith Busch wrote:
> > I tried to list out conditions for when I think the value could be counted on here:
> > 
> >   https://lore.kernel.org/linux-nvme/aGvuRS8VmC0JXAR3@kbusch-mbp/
> > 
> Regarding the checks you listed, they seem too restrictive. They only support
> AWUPF for single-controller devices and for disks that either have only one
> namespace or support formatting all namespaces together (i.e., do not support
> formatting individual namespaces).

Being restrictive was the point. It constrains to 1.0 type behavior
where things were much simpler. I am just shocked vendors went through
the trouble to implement the complicated features but couldn't be
bothered to do the trivial one that makes it useful.