linux-kernel - Re: [PATCH] nvme: remove multipath module parameter

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: <Z7Sh-3yHbXVmRbNL@kbusch-mbp>
Date: Tue, 18 Feb 2025 08:06:35 -0700
From: Keith Busch <kbusch@...nel.org>
To: John Meneghini <jmeneghi@...hat.com>
Cc: hch@....de, sagi@...mberg.me, bmarzins@...hat.com,
	Bryan Gurney <bgurney@...hat.com>, linux-nvme@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Marco Patalano <mpatalan@...hat.com>,
	axboe@...nel.dk
Subject: Re: [PATCH] nvme: remove multipath module parameter

On Thu, Feb 13, 2025 at 03:37:28PM -0500, John Meneghini wrote:
> Keith, Christoph and Sagi,
> 
> This patch has been fully tested and analyzed by Red Hat's QA group and no
> unexpected side effects or regressions have been found. Both NVMe/FC and NVMe/TCP
> have been tested. Our QE engineer has asked me to report this upstream.

What's the harm in leaving the parameter? *I* use it so I can test both
ways without needing to compile multiple kernels.