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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <58519c4e-5801-4481-9087-be4f19b218f7@redhat.com>
Date: Fri, 22 Nov 2024 13:29:57 -0500
From: John Meneghini <jmeneghi@...hat.com>
To: Keith Busch <kbusch@...nel.org>
Cc: Christoph Hellwig <hch@....de>, Bryan Gurney <bgurney@...hat.com>,
 linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
 sagi@...mberg.me, axboe@...nel.dk, mpe@...erman.id.au, naveen@...nel.org,
 maddy@...ux.ibm.com, kernel@...0n.name, bmarzins@...hat.com
Subject: Re: [PATCH 1/1] nvme: always enable multipath

On 11/22/24 13:15, Keith Busch wrote:> If you want to change the driver to prevent exposing subsequent
> namepsace path block devices when multipath is not enabled, that is
> probably fine.

OK, we'll work on another patch to do this. The plan will be:

When CONFIG_NVME_MULTIPATH=y, you get multipath.c and full support for both nvme multipath (CMIC/NMIC = 1) and non-multipath 
devices (CMIC/NMIC=0) devices with 1 /dev entry per namespace.

When CONFIG_NVME_MULTIPATH=n, you get support for non-multipath devices (CMIC/NMIC=0) devices, but multipath devices 
(CMIC/NMIC=1) will only expose the first controller/namespace path.

/John