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] [thread-next>] [day] [month] [year] [list]

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

On Wed, Aug 20, 2025 at 03:02:20PM +0000, John Garry wrote:
> It would be preferred to stop honouring AWUPF altogether, but this may
> needlessly disable atomic write support for many "good" devices which
> only specify AWUPF. Currently all validation of controller-related
> atomics limits is dropped.

These "good" devices that only report AWUPF, is there some set of
characteristics that generally applies to all of them? 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/

I just don't know if you know of any devices where that criteria doesn't
git. If not, maybe we can work with that without introducing more user
knobs.