linux-kernel - Re: [PATCH] drivers/nvme/host/pci: Fix the asynchronous detection issue of nvme devices

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 for Android: free password hash cracker in your pocket

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

Message-ID: <58c289ef-770b-4524-b38d-ebdb51ccc8f4@acm.org>
Date: Thu, 24 Jul 2025 09:07:29 -0700
From: Bart Van Assche <bvanassche@....org>
To: likunyu10 <likunyu10@....com>, kbusch@...nel.org, axboe@...nel.dk,
 hch@....de, sagi@...mberg.me
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
 likunyu15 <likunyu15@...com>
Subject: Re: [PATCH] drivers/nvme/host/pci: Fix the asynchronous detection
 issue of nvme devices

On 7/20/25 11:51 AM, likunyu10 wrote:
> PROBE_PREFER_ASYNCHRONOUS asynchronous detection has a significant impact
> on important devices. For example, if a server has two or more nvme disk
> devices, it can cause disk loading disorder, which can also have a
> certain impact on actual production environments.

That's intentional. Please fix your user space code that uses hard-coded
NVMe block device names or introduce a mechanism in user space for block
devices that is similar to the predictable network interface names
mechanism. See also https://systemd.io/PREDICTABLE_INTERFACE_NAMES/.

Bart.