linux-kernel - Re: [PATCH RESEND v11 10/13] um: nommu: a work around for MMU dependency to PCI driver

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: <23adb61e95275251e459513a03ab7d2bcf1f2e07.camel@sipsolutions.net>
Date: Tue, 23 Sep 2025 19:13:47 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Geert Uytterhoeven <geert@...ux-m68k.org>, Hajime Tazaki
	 <thehajime@...il.com>
Cc: linux-um@...ts.infradead.org, ricarkol@...gle.com,
 Liam.Howlett@...cle.com, 	linux-kernel@...r.kernel.org, Arnd Bergmann
 <arnd@...db.de>
Subject: Re: [PATCH RESEND v11 10/13] um: nommu: a work around for MMU
 dependency to PCI driver

On Tue, 2025-09-23 at 17:42 +0200, Geert Uytterhoeven wrote:
> > 
> > currently, drivers/pci/Kconfig (CONFIG_PCI) marks as depends on MMU,
> > so we cannot select it when CONFIG_MMU=n.
> 
> That is a fairly recent change, see commit 8fe743b5eba0abfb ("PCI:
> Add CONFIG_MMU dependency") in v6.16-rc1.  As this is not a "hard"
> dependency, perhaps it should be reverted, iff you are willing to take
> care of the casual breakage?

Why though? UML with PCI can't really be a functional thing, only a
testing thing, and testing PCI on !MMU when that is actually impossible
in non-simulation is pointless?

johannes