From: sashiko-bot@kernel.org
To: "Christopher Lusk" <clusk@northecho.dev>
Cc: linux-serial@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] selftests/landlock: cover TIOCSIG signal scoping
Date: Sun, 13 Sep 2026 22:26:22 +0000 [thread overview]
Message-ID: <20260913222623.3E9351F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260913221958.839429-3-clusk@northecho.dev>
> Add a focused regression test for a sandboxed PTY master holder using
> TIOCSIG to signal an out-of-domain slave foreground process group.
>
> The test observes both the ioctl result and the target's signal-handler
> effect. It fails on the unpatched base because TIOCSIG succeeds and
> SIGTSTP is delivered. It passes with the preceding RFC prototype because
> the ioctl fails with EPERM and the target observes no signal.
>
> The identical test binary and initramfs were booted against both kernels
> under QEMU. TAP reported one failing test on the affected image and one
> passing test on the patched image.
>
> Assisted-by: Claude:claude-opus-4-8
> 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/20260913221958.839429-1-clusk@northecho.dev?part=2
prev parent reply other threads:[~2026-09-13 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 22:19 [RFC PATCH 0/2] Landlock signal scope and TIOCSIG Christopher Lusk
2026-09-13 22:19 ` [RFC PATCH 1/2] tty: mediate TIOCSIG through task_kill LSM hooks Christopher Lusk
2026-09-13 22:37 ` sashiko-bot
2026-09-13 22:19 ` [RFC PATCH 2/2] selftests/landlock: cover TIOCSIG signal scoping Christopher Lusk
2026-09-13 22:26 ` 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=20260913222623.3E9351F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=clusk@northecho.dev \
--cc=linux-serial@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