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: <Z-bcXHLwqU8aI_Ug@kbusch-mbp.dhcp.thefacebook.com>
Date: Fri, 28 Mar 2025 11:29:00 -0600
From: Keith Busch <kbusch@...nel.org>
To: John Meneghini <jmeneghi@...hat.com>
Cc: hch@....de, 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 v2 0/3] nvme: make core.nvme_multipath configurable

On Sat, Mar 22, 2025 at 07:28:45PM -0400, John Meneghini wrote:
> These patches propose an alternative to the outright removal of the nvme
> core multipath module parameter. Rather than deleting this module
> parameter we control its appearance with a new Kconfig option named
> NVME_MULTIPATH_PARAM
> 
> Note that the default kernel config settings produce a kernel
> with no change in functionality. By default both NVME_MULTIPATH
> and NVME_MULTIPATH_PARAM are enabled and there are no user visable
> changes.
> 
> To remove the core.nvme_multipath parameter simply compile with
> CONFIG_NVME_MULTIPATH_PARAM=n.

Thanks, patches 1 and 3 are applied.

Lacking a better way to handle your situation, we can add patch 2. But I
recall you wanted to invert the logic and option name, so I'll wait for
that.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ