From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v3 2/2] selftests/landlock: cover TTY signal scoping
Date: Wed, 23 Sep 2026 16:42:40 +0000 [thread overview]
Message-ID: <20260923164240.B91E21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923163321.79770-3-clusk@northecho.dev>
> LANDLOCK_SCOPE_SIGNAL blocks signaling an arbitrary out-of-domain process,
> but a PTY master retains signal delivery to its terminal foreground process
> group.
>
> Add a test that enters a signal-scoped domain, checks that kill(SIGUSR1)
> is denied with EPERM, and checks that TIOCSIG(SIGTSTP) succeeds and reaches
> the target's signal handler.
>
> Tested the focused case in three QEMU boots and ran the complete Landlock
> selftest suite (12 programs, no failures). Built all Landlock selftests
> with W=1.
>
> Link: https://lore.kernel.org/r/20260916152336.1589383-1-clusk@northecho.dev
> Suggested-by: Günther Noack <gnoack@google.com>
> Suggested-by: Mickaël Salaün <mic@digikod.net>
> Assisted-by: Codex:gpt-5.6-sol
> Signed-off-by: Christopher Lusk <clusk@northecho.dev>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923163321.79770-1-clusk@northecho.dev?part=2
prev parent reply other threads:[~2026-09-23 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 16:33 [PATCH v3 0/2] landlock: clarify TTY signal scoping Christopher Lusk
2026-09-23 16:33 ` [PATCH v3 1/2] docs: " Christopher Lusk
2026-09-23 16:39 ` sashiko-bot
2026-09-23 16:33 ` [PATCH v3 2/2] selftests/landlock: cover " Christopher Lusk
2026-09-23 16:42 ` 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=20260923164240.B91E21F000FF@smtp.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.