| 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
| ||
|
Message-ID: <03e7cc64-fafd-405e-a07a-4bc6d0e1d743@redhat.com> Date: Tue, 11 Mar 2025 22:35:40 -0400 From: John Meneghini <jmeneghi@...hat.com> To: Christoph Hellwig <hch@....de> Cc: kbusch@...nel.org, sagi@...mberg.me, loberman@...hat.com, linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org, emilne@...hat.com, bgurney@...hat.com Subject: Re: [PATCH 2/4] nvme-multipath: add the NVME_MULTIPATH_PARAM config option On 3/5/25 9:33 AM, Christoph Hellwig wrote: > On Thu, Feb 27, 2025 at 10:25:39PM -0500, John Meneghini wrote: >> The NVME_MULTIPATH_PARAM option controls the core.nvme_multipath module >> parameter. When NVME_MULTIPATH_PARAM=n the multipath parameter is removed >> and core nvme multipathing is enabled. When NVME_MULTIPATH_PARAM=y >> the multipath parameter is added and multipath support becomes >> configurable with the core.nvme_multipath parameter. > > What's the point of adding yet another confusing option? If you'll read the kConfig description, hopefully it's not confusing. The whole point of this patch series is to remove the core.nvme_mulipath parameter. This is what the patch at: https://lore.kernel.org/linux-nvme/20250204211158.43126-1-bgurney@redhat.com/ does, and this is what this patch does. Since people didn't want to remove core.nvme_multipath parameter in https://lore.kernel.org/linux-nvme/20250204211158.43126-1-bgurney@redhat.com/ I've proposed this patch as an alternative. It provides a kConfig option to remove the core.nvme_multipath parameter so those who want it can keep it, and those who don't and compile it out. /John
Powered by blists - more mailing lists