From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Hallgrimur H. Gunnarsson" <halg@google.com>
Cc: "Christian Brauner" <brauner@kernel.org>,
"Serge Hallyn" <sergeh@kernel.org>,
"Andy Lutomirski" <luto@kernel.org>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"David Howells" <dhowells@redhat.com>,
"Kees Cook" <kees@kernel.org>, "Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Jonathan Calmels" <jcalmels@3xx0.net>,
"Jann Horn" <jannh@google.com>,
"Günther Noack" <gnoack@google.com>,
"KP Singh" <kpsingh@kernel.org>,
"Casey Schaufler" <casey@schaufler-ca.com>,
linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org, linux-api@vger.kernel.org,
containers@lists.linux.dev, keyrings@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] userns: introduce capability bounding set for user namespaces
Date: Thu, 19 Nov 2026 22:14:16 +0200 [thread overview]
Message-ID: <av9YmPJexMJoCGWO@kernel.org> (raw)
In-Reply-To: <av9L2ez51erKkQNo@google.com>
On Thu, Nov 19, 2026 at 07:19:53PM +0000, Hallgrimur H. Gunnarsson wrote:
> On Thu, Nov 19, 2026 at 05:05:26PM +0200, Jarkko Sakkinen wrote:
> > On Thu, Nov 19, 2026 at 10:42:05AM +0000, Hallgrimur H. Gunnarsson wrote:
> > > static void set_cred_user_ns(struct cred *cred, struct user_namespace *user_ns)
> >
> > I read the diff through but this led me to dead end. Cannot find this
> > function from anywhere. I look the changes again once this is sorted
> > out becaus this is interesting.
> >
> > I wanted to look at the call site to understand how cap_bset gets set,
> > which is not now possible but I do get the gist and agree with it.
>
> Thanks for taking a look. The series is based on v7.4-rc1 and
> set_cred_user_ns() lives in kernel/user_namespace.c, where it is called
> from create_user_ns() and userns_install(). ns->cap_bset itself is
> initialized in create_user_ns() right before calling set_cred_user_ns().
>
> > I'd figure getting this relates to my rootns patches (perhas). One key
> > mechanism for me resolving the unprivileged in my use case is
> > MOVE_MOUNT_T_MNTNS [1], which is orthogonal but just pointing out
> > the problem space.
>
> From a quick look, they appear complementary. Being able to do more
> setup operations from the outside generally aligns with bounding
> capabilities inside the user namespace.
>
> > I read through https://lwn.net/Articles/978846/ to understand the topic
> > overall. Just mentionining as a possible addition to the cover letter
> > (not a priority/necessity).
>
> That LWN article is actually linked in the cover letter as [2].
>
> > Hope these help and can be kept in the loop :-)
>
> Will do, I'll keep you CC'd on future revisions.
Thank you.
Br, Jarkko
next prev parent reply other threads:[~2026-11-19 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 10:42 [PATCH v2 0/4] userns: per-namespace capability bounding set Hallgrimur H. Gunnarsson
2026-11-19 10:42 ` [PATCH v2 1/4] userns: introduce capability bounding set for user namespaces Hallgrimur H. Gunnarsson
2026-11-19 11:11 ` sashiko-bot
2026-11-20 11:35 ` Hallgrimur H. Gunnarsson
2026-11-19 15:05 ` Jarkko Sakkinen
2026-11-19 19:19 ` Hallgrimur H. Gunnarsson
2026-11-19 20:14 ` Jarkko Sakkinen [this message]
2026-11-19 22:52 ` Andy Lutomirski
2026-11-20 17:09 ` Andy Lutomirski
2026-11-19 10:42 ` [PATCH v2 2/4] capability: bound ptrace and cred subset checks by userns ceilings Hallgrimur H. Gunnarsson
2026-11-19 10:51 ` sashiko-bot
2026-11-19 10:42 ` [PATCH v2 3/4] proc: expose userns capability mask as CapUns in /proc/<pid>/status Hallgrimur H. Gunnarsson
2026-11-19 10:46 ` sashiko-bot
2026-11-19 10:42 ` [PATCH v2 4/4] selftests/capabilities: add userns capability bounding set tests Hallgrimur H. Gunnarsson
2026-11-19 10:47 ` sashiko-bot
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=av9YmPJexMJoCGWO@kernel.org \
--to=jarkko@kernel.org \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=containers@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=gnoack@google.com \
--cc=halg@google.com \
--cc=jannh@google.com \
--cc=jcalmels@3xx0.net \
--cc=jmorris@namei.org \
--cc=kees@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=rdunlap@infradead.org \
--cc=sergeh@kernel.org \
--cc=skhan@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.