From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: John Ericson <mail@johnericson.me>,
Andy Lutomirski <luto@kernel.org>, Li Chen <me@linux.beauty>,
Cong Wang <cwang@multikernel.io>,
linux-arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Jan Kara <jack@suse.cz>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <kees@kernel.org>,
Sergei Zimmerman <sergei@zimmerman.foo>,
Farid Zakaria <farid.m.zakaria@gmail.com>
Subject: Re: [RFC] Null Namespaces
Date: Mon, 29 Jun 2026 12:31:33 +0200 [thread overview]
Message-ID: <20260629-parabel-kraut-waldsee-a4ebfab949ee@brauner> (raw)
In-Reply-To: <20260626001538.GO2636677@ZenIV>
> So supply a library of your own and try to convince people to use it
> instead of libc. You'll have to anyway, seeing that a large and
I agree. And in fact that is what we've been doing:
https://github.com/cyphar/libpathrs
I also plan on splitting the chase*() machinery in systemd out as
a separate C library as well:
https://github.com/systemd/systemd/blob/104750fd60da4c563650785e272a7ce0a6694d01/src/basic/chase.c#L238
> hard-to-predict part of libc will be non-functional. Which syscalls
> are used by your library is entirely up to you.
>
> Would that kind of thing added kernel-side assist the development of such
> library? Maybe, but I wouldn't bet too much on that - if you start from
It wouldn't really and we haven't needed it for that.
next prev parent reply other threads:[~2026-06-29 10:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 22:51 [RFC] Null Namespaces John Ericson
2026-06-24 23:06 ` Andy Lutomirski
2026-06-24 23:20 ` Andy Lutomirski
2026-06-24 23:53 ` John Ericson
2026-06-25 1:10 ` Al Viro
2026-06-25 3:41 ` John Ericson
2026-06-25 15:51 ` Andy Lutomirski
2026-06-25 18:21 ` John Ericson
2026-06-26 0:15 ` Al Viro
2026-06-26 16:26 ` John Ericson
2026-06-29 10:31 ` Christian Brauner [this message]
2026-06-24 23:12 ` Al Viro
2026-06-25 21:00 ` H. Peter Anvin
2026-06-25 21:50 ` John Ericson
2026-06-25 23:09 ` Andy Lutomirski
2026-06-26 8:27 ` David Laight
2026-06-26 17:23 ` John Ericson
2026-06-29 10:39 ` Christian Brauner
2026-07-01 9:49 ` Jori Koolstra
2026-07-02 21:28 ` H. Peter Anvin
2026-06-29 11:45 ` Christian Brauner
2026-06-29 21:06 ` Andy Lutomirski
2026-06-30 4:25 ` John Ericson
2026-07-02 9:34 ` Christian Brauner
2026-07-02 15:43 ` John Ericson
2026-07-03 8:59 ` Christian Brauner
2026-07-03 17:35 ` Directory capability brain dump (Re: [RFC] Null Namespaces) Andy Lutomirski
2026-07-06 14:52 ` [RFC] Null Namespaces Christian Brauner
2026-07-06 16:32 ` Jann Horn
2026-07-06 17:10 ` Andy Lutomirski
2026-07-06 17:04 ` Andy Lutomirski
2026-06-30 2:50 ` John Ericson
2026-06-30 7:14 ` Christian Brauner
2026-06-30 17:20 ` John Ericson
2026-06-30 17:41 ` Andy Lutomirski
2026-07-02 9:29 ` Christian Brauner
2026-06-30 18:05 ` H. Peter Anvin
2026-07-04 13:20 ` Li Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260629-parabel-kraut-waldsee-a4ebfab949ee@brauner \
--to=brauner@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=cwang@multikernel.io \
--cc=dave.hansen@linux.intel.com \
--cc=farid.m.zakaria@gmail.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mail@johnericson.me \
--cc=me@linux.beauty \
--cc=mingo@redhat.com \
--cc=sergei@zimmerman.foo \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox