From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v6 6/8] selftests/landlock: Add capability restriction tests
Date: Wed, 14 Oct 2026 08:43:17 +0000 [thread overview]
Message-ID: <sashiko-outbox-171034@kernel.org> (raw)
In-Reply-To: <20261014082718.1435842-7-mic@digikod.net>
> Add tests to exercise LANDLOCK_PERMISSION_CAPABILITY_USE enforcement. A
> sandboxed process is denied a handled capability when no rule grants it,
> and an explicit rule restores it. Unknown capability values above
> CAP_LAST_CAP are accepted at rule-add time yet have no runtime effect,
> because deny-by-default still applies once the domain is enforced.
> Stacking tests cover the per-layer allow/deny combinations, including a
> layer that does not handle the permission, and invalid rule attributes
> return the expected errors.
>
> Three tests exercise non-standard capability contexts: enforcing a
> domain via CAP_SYS_ADMIN authorization without no_new_privs, restricting
> capabilities gained through the kernel's user namespace ownership bypass
> (cap_capable_helper), and checking CAP_SYS_ADMIN against a descendant
> user namespace, with an unsandboxed positive control, to confirm the
> decision is independent of the target.
>
> Audit tests verify denied and allowed capabilities, per-member quiet
> interactions, and CAP_OPT_NOAUDIT suppression. Trace tests cover
> accepted, rejected, and no-op rule adds, and normal, quiet, and
> CAP_OPT_NOAUDIT denials.
>
> Test coverage for security/landlock is 91.8% of 2864 lines according to
> LLVM 22.
>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Günther Noack <gnoack@google.com>
> Cc: Paul Moore <paul@paul-moore.com>
> Cc: Serge E. Hallyn <serge@hallyn.com>
> Signed-off-by: Mickaël Salaün <mic@digikod.net>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014082718.1435842-1-mic@digikod.net?part=6
next prev parent reply other threads:[~2026-10-14 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:27 [PATCH v6 0/8] Landlock: Namespace and capability control Mickaël Salaün
2026-10-14 8:27 ` [PATCH v6 1/8] landlock: Rename quiet_masks to quiet_access Mickaël Salaün
2026-10-14 8:33 ` sashiko-bot
2026-10-14 8:27 ` [PATCH v6 2/8] landlock: Wrap per-layer access masks in struct layer_config Mickaël Salaün
2026-10-14 8:32 ` sashiko-bot
2026-10-14 8:27 ` [PATCH v6 3/8] landlock: Enforce namespace use restrictions Mickaël Salaün
2026-10-14 8:39 ` sashiko-bot
2026-10-14 8:27 ` [PATCH v6 4/8] landlock: Enforce capability restrictions Mickaël Salaün
2026-10-14 8:36 ` sashiko-bot
2026-10-14 8:27 ` [PATCH v6 5/8] selftests/landlock: Add namespace restriction tests Mickaël Salaün
2026-10-14 8:41 ` sashiko-bot
2026-10-14 8:27 ` [PATCH v6 6/8] selftests/landlock: Add capability " Mickaël Salaün
2026-10-14 8:43 ` sashiko-bot [this message]
2026-10-14 8:27 ` [PATCH v6 7/8] samples/landlock: Add capability and namespace restriction support Mickaël Salaün
2026-10-14 8:45 ` sashiko-bot
2026-10-14 8:27 ` [PATCH v6 8/8] landlock: Add documentation for capability and namespace restrictions Mickaël Salaün
2026-10-14 8:43 ` 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=sashiko-outbox-171034@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).