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: <Z7UYGc25aKFL6oFj@kbusch-mbp>
Date: Tue, 18 Feb 2025 16:30:33 -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, Randy Jennings <randyj@...estorage.com>
Subject: Re: [PATCH] nvme: remove multipath module parameter

On Tue, Feb 18, 2025 at 06:06:05PM -0500, John Meneghini wrote:
> OK, maybe you have a use case in mind. I'll assume you do: some
> applications want to disable native nvme multipathing and to see
> all namespace paths in user space, and they are using this parameter
> to do it. These are ostensibly user space MP applications.

You can have a ublk frontend device with individual namespace paths on
the backend, and let ublkserver do whatever it wants with them.

> So what happens when one of these user space MP applications needs
> a change or a bug bug fix in the kernel?  Are those patches being
> merged into the kernel under a different auspices... is it just
> DMMP that we don't want to enable support for?

I think patches exporting driver private information is a pretty clear
indicator it's for stacking drivers.