From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH v3 2/2] selftests/landlock: Test PR_SET_SECUREBITS mediation
Date: Wed, 18 Nov 2026 14:59:56 +0000 [thread overview]
Message-ID: <sashiko-outbox-221277@kernel.org> (raw)
In-Reply-To: <20261118145431.2551578-3-mic@digikod.net>
> Test that Landlock denies and logs a privileged PR_SET_SECUREBITS
> change, now that the previous commit routes its CAP_SETPCAP check
> through the capable hooks, and that an unprivileged change still
> succeeds. The domain deallocation record must then report exactly one
> denial, which proves that the unprivileged change was not denied,
> without relying on a no-record timeout.
>
> The check-exec selftests already cover commoncap's securebits semantics.
> Without the previous commit, this test fails.
>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Günther Noack <gnoack@google.com>
> Cc: Paul Moore <paul@paul-moore.com>
> Cc: Serge Hallyn <serge@hallyn.com>
> Signed-off-by: Mickaël Salaün <mic@digikod.net>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261118145431.2551578-1-mic@digikod.net?part=2
prev parent reply other threads:[~2026-11-18 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:54 [PATCH v3 0/2] Fix LSM mediation of PR_SET_SECUREBITS Mickaël Salaün
2026-11-18 14:54 ` [PATCH v3 1/2] capabilities: Check PR_SET_SECUREBITS with ns_capable() Mickaël Salaün
2026-11-18 15:00 ` sashiko-bot
2026-11-18 14:54 ` [PATCH v3 2/2] selftests/landlock: Test PR_SET_SECUREBITS mediation Mickaël Salaün
2026-11-18 14:59 ` 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-221277@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=selinux@vger.kernel.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.