From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 4/4] selftests/capabilities: add userns capability bounding set tests
Date: Thu, 19 Nov 2026 10:47:50 +0000 [thread overview]
Message-ID: <sashiko-outbox-222984@kernel.org> (raw)
In-Reply-To: <20261119104208.782900-5-halg@google.com>
> Add selftests in tools/testing/selftests/capabilities covering:
>
> - prctl(PR_CAP_USERNS) argument validation and authorization rules for
> lowering, clearing, and raising capabilities.
> - Default full capability grants, cap_userns restrictions (including
> clearing all capabilities), and monotonic inheritance across nested
> user namespaces.
> - Default retention of capabilities in cap_permitted, and strict
> enforcement and persistence of SECBIT_CAP_USERNS_STRICT and its lock
> across user namespace transitions.
> - Credential and cap_userns clamping upon entering a user namespace via
> setns().
> - Implicit parent-owner capability bounding by the owned namespace's
> cap_bset (including over descendants) and the caller's userns
> ceiling, while preserving explicit ancestor capabilities.
> - Ptrace restrictions across PTRACE_ATTACH, PTRACE_TRACEME, and
> PTRACE_MODE_READ for same-userns peers and owned descendant
> namespaces, while preserving explicit CAP_SYS_PTRACE.
> - Preservation of dumpable and pdeath_signal when narrowing the userns
> ceiling and resets when widening it.
> - CapUns reporting in /proc/self/status.
>
> Signed-off-by: Hallgrimur H. Gunnarsson <halg@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261119104208.782900-1-halg@google.com?part=4
prev parent reply other threads:[~2026-11-19 10:47 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
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 [this message]
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=sashiko-outbox-222984@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.