linux-kernel - Re: [PATCH 1/1] nvme: always enable multipath

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: <20241122120925.GA25817@lst.de>
Date: Fri, 22 Nov 2024 13:09:25 +0100
From: Christoph Hellwig <hch@....de>
To: Bryan Gurney <bgurney@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
	kbusch@...nel.org, hch@....de, sagi@...mberg.me, axboe@...nel.dk,
	mpe@...erman.id.au, naveen@...nel.org, maddy@...ux.ibm.com,
	kernel@...0n.name, jmeneghi@...hat.com, bmarzins@...hat.com
Subject: Re: [PATCH 1/1] nvme: always enable multipath

On Thu, Nov 21, 2024 at 05:03:21PM -0500, Bryan Gurney wrote:
> Since device-mapper multipath will no longer be operating on NVMe
> devices, there is no longer a need to set CONFIG_NVME_MULTIPATH=n.
> 
> Always enable NVMe multipath, remove CONFIG_NVME_MULTIPATH, and use
> the code paths that would be used if CONFIG_NVME_MULTIPATH=y.

As mentioned last round not having to build the not tiny multipath
code for embedded systems and other small builds that never require
multipathing still seems like a sensible idea.