Re: [LSF/MM/BPF TOPIC] Namespace-aware upcalls from kernel filesystems
Shyam Prasad N <[email protected]>
| Newsgroups | org.kernel.vger.keyrings,org.kernel.vger.linux-cifs,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-nfs |
|---|---|
| Message-ID | <CANT5p=p6yw3eYJVXZc2CA2fBgBYpZ4W0uKivt2tCmtgos3GVdw@mail.gmail.com> |
On Mon, Feb 16, 2026 at 6:25 AM David Leadbeater <[email protected]> wrote: > > On Sat, Feb 14, 2026 at 03:36:22PM +0530, Shyam Prasad N wrote: > > I tried to prototype a namespace aware upcall mechanism for kernel keys here: > > https://www.spinics.net/lists/keyrings/msg17581.html > > But it has not been successful so far. I'm seeking reviews on this > > approach from security point of view. > > I have more context from the containers side, but to me this doesn't > appear safe. Entering the right namespaces isn't enough to safely run > code within a container. The container runtime may have set up seccomp > or other limits which this upcall won't respect. Hi David, Thanks for these comments. Let me look into seccomp to see if kernel will have any visibility into it. > > I would like to see a solution to this though, we currently have custom > callback code to make this work. I'm not familiar enough with the > interfaces but an approach where something registers also seems > desirable because it is able to preserve backwards compatibility, which > changing the namespace the upcall runs in doesn't. Ack. Will explore the options and get back to this thread. > > David > -- Regards, Shyam