Re: misc/60956: ramdisk-cgdroot.fs seems to check for /libdata/firmware/ in the ram disk rather than the mounted cgdroot

["Martin Husemann via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR misc/60956; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: Taylor R Campbell <riastradh%NetBSD.org@localhost>
Cc: "David H. Gutteridge" <david%gutteridge.ca@localhost>, Ellie <el%horse64.org@localhost>,
	gnats-bugs%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Subject: Re: misc/60956: ramdisk-cgdroot.fs seems to check for
 /libdata/firmware/ in the ram disk rather than the mounted cgdroot
Date: Tue, 3 Nov 2026 15:42:22 +0100

 On Tue, Nov 03, 2026 at 02:35:52PM +0000, Taylor R Campbell wrote:
 > This doesn't help.  Whether userland does chroot or mounts a pivot
 > root or dances the waltz, the kernel doesn't know (a) that instead of
 > running config_mountroot hooks as soon as cgdroot.fs is mounted, it
 > has to wait for userland to mount the real root; or (b) when userland
 > has mounted the real root and it can finally run the config_mountroot
 > hooks.
 
 Right, it helps only for drivers that do it at first ifconfig up time
 or similar.
 
 For others we could decouple the config_mountroot() and the "hey this
 is a good time to (re-)try loading your firmware" event, and then
 send that event at config_mountroot() time but also (again) at pivot
 time. For chroots we probably don't want to do that for security reasons.
 
 Martin