From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v1 net-next 1/4] selftests: landlock: Replace MSG_OOB with O_ASYNC+F_SETSIG.
Date: Tue, 17 Nov 2026 02:19:00 +0000 [thread overview]
Message-ID: <sashiko-outbox-218076@kernel.org> (raw)
In-Reply-To: <20261116021845.2533130-2-kuniyu@google.com>
> AF_UNIX will drop MSG_OOB support.
>
> scoped_signal_test.c uses MSG_OOB in fown.sigurg_socket and
> trace_fown.deny_scope_fown to trigger SIGURG and exercise
> security_file_send_sigiotask().
>
> The same hook can be exercised via send_sigio() with a plain send()
> by setting O_ASYNC and F_SETSIG with SIGURG on recv_socket.
>
> Let's replace MSG_OOB with O_ASYNC and F_SETSIG so that the tests
> do not depend on CONFIG_AF_UNIX_OOB.
>
> Note that with O_ASYNC set on recv_socket, closing client_socket
> while recv_socket is still open also triggers SIGURG for POLL_HUP
> in unix_release_sock(), which would emit an extra
> landlock_deny_scope_signal trace event in
> trace_fown.deny_scope_fown. Thus, the child waits for the parent
> to close recv_socket via pipe_parent before closing client_socket.
>
> Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261116021845.2533130-1-kuniyu@google.com?part=1
prev parent reply other threads:[~2026-11-17 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261116021845.2533130-1-kuniyu@google.com>
2026-11-16 2:18 ` [PATCH v1 net-next 1/4] selftests: landlock: Replace MSG_OOB with O_ASYNC+F_SETSIG Kuniyuki Iwashima
2026-11-17 2:19 ` 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-218076@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