Re: [RFC PATCH v2 00/13] Namespace for namespace roots
From: Jarkko Sakkinen
Date: Fri Nov 20 2026 - 09:03:37 EST
On Fri, Nov 20, 2026 at 02:24:57PM +0100, Alexander Mikhalitsyn wrote:
> Yeah, detached mounts API solves a security issue here, but it does not
> fully enable the use-case Andy describes (if I understood it
> correctly). My interpretation here is that to fully cover it we need
> some well-isolated communication channel between container and
> container manager (vsock for containers? :-D). And some well-defined
> agreement of how PID 1 inside the container can get an information
> about a hotplugg-ed stuff. [ But it could be that I completely
> misunderstood and Andy meant something much more simple here. ]
I guess you are right, It is good to check that in detail. I'm figuring
out if I can test run it to some near confirmable level.
It has enough steps that it cannot be simply "explained away" so yeah
thanks for pointing that out.
I'm going to use an old NUC for this as I recently made my kernel test
harness installable bootc operating system. This was minimum working
environment for Matthew Garrett's lockdown-hibernate patches, and took
over a month to setup. Great that it gets more use :-) [1]
I think these type of use cases are also best to test with real hardware
over QEMU up until some guarantees are in place, so I'll just go ahead
and do that...
>
> Kind regards,
> Alex
[1] https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd-test.git/
Br, Jarkko