From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v3 2/5] landlock: Add KUnit test for landlock_get_fs_access_mask()
Date: Fri, 13 Nov 2026 20:37:34 +0000 [thread overview]
Message-ID: <sashiko-outbox-213658@kernel.org> (raw)
In-Reply-To: <20261113-b4-landlock-refer-nonfs-layer-v3-2-02d7e42bcdfd@gmail.com>
> This checks that landlock_upgrade_handled_layer_config() and
> landlock_get_fs_access_mask() together result in the right handled
> access rights being reported by landlock_get_fs_access_mask():
> LANDLOCK_ACCESS_FS_REFER is only implicit if any of the other
> filesystem access rights are handled.
>
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-b4-landlock-refer-nonfs-layer-v3-0-02d7e42bcdfd@gmail.com?part=2
next prev parent reply other threads:[~2026-11-13 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 20:23 [PATCH v3 0/5] landlock: Fix REFER in layered domains Günther Noack
2026-11-13 20:23 ` [PATCH v3 1/5] landlock: Fix layer composition of LANDLOCK_ACCESS_FS_REFER Günther Noack
2026-11-13 20:32 ` sashiko-bot
2026-11-13 20:23 ` [PATCH v3 2/5] landlock: Add KUnit test for landlock_get_fs_access_mask() Günther Noack
2026-11-13 20:37 ` sashiko-bot [this message]
2026-11-13 20:23 ` [PATCH v3 3/5] selftests/landlock: Test that layering does not break refer Günther Noack
2026-11-13 20:44 ` sashiko-bot
2026-11-13 20:23 ` [PATCH v3 4/5] landlock: Simplify landlock_get_fs_access_mask() Günther Noack
2026-11-13 20:47 ` sashiko-bot
2026-11-13 20:23 ` [PATCH v3 5/5] landlock: Clarify implicit handling of LANDLOCK_ACCESS_FS_REFER Günther Noack
2026-11-13 20:49 ` 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-213658@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.