From: Alejandro Colomar <alx@kernel.org>
To: funsafemath <funsafemath@proton.me>
Cc: linux-man@vger.kernel.org, Tycho Andersen <tycho@tycho.ws>
Subject: Re: [PATCH 1/2] man/man2/seccomp.2: Document SECCOMP_FILTER_FLAG_TSYNC_ESRCH
Date: Sat, 16 May 2026 23:38:48 +0200 [thread overview]
Message-ID: <agjag_tIzuKpME-B@devuan> (raw)
In-Reply-To: <agjZM97qL3w4JZBX@nix-mail>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
Hi,
On 2026-05-16T21:53:17+0100, funsafemath wrote:
> Document SECCOMP_FILTER_FLAG_TSYNC_ESRCH flag, which allows to
> use SECCOMP_FILTER_FLAG_TSYNC and SECCOMP_FILTER_FLAG_NEW_LISTENER
> flags together by returning ESRCH on synchronization error instead
> of the thread ID.
>
> <https://lore.kernel.org/r/20200304180517.23867-1-tycho@tycho.ws>
> ---
Would you mind signing the patch?
> man/man2/seccomp.2 | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/man/man2/seccomp.2 b/man/man2/seccomp.2
> index 75c7b2d58..0729a653c 100644
> --- a/man/man2/seccomp.2
> +++ b/man/man2/seccomp.2
> @@ -241,6 +241,21 @@ .SH DESCRIPTION
> .B SECCOMP_MODE_STRICT
> or if it has attached new seccomp filters to itself,
> diverging from the calling thread's filter tree.
> +.TP
> +.BR SECCOMP_FILTER_FLAG_TSYNC_ESRCH " (since Linux 5.7)"
> +.\" commit 51891498f2da78ee64dfad88fa53c9e85fb50abf
> +Return
> +.B ESRCH
I expect that in user space, we'll see -1 in the return value, and ESRCH
in errno, right? If so, we should say "Fail with ESRCH ...".
> +instead of the thread ID on synchronization failure if
> +.B SECCOMP_FILTER_FLAG_TSYNC
Spurious double space. s/ / /
Have a lovely day!
Alex
> +was specified.
> +.IP
> +If this flag is not set, using
> +.B SECCOMP_FILTER_FLAG_NEW_LISTENER
> +and
> +.B SECCOMP_FILTER_FLAG_TSYNC
> +flags together results in
> +.BR EINVAL .
> .RE
> .TP
> .BR SECCOMP_GET_ACTION_AVAIL " (since Linux 4.14)"
> --
> 2.52.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-16 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 20:53 [PATCH 1/2] man/man2/seccomp.2: Document SECCOMP_FILTER_FLAG_TSYNC_ESRCH funsafemath
2026-05-16 21:38 ` Alejandro Colomar [this message]
2026-05-18 14:04 ` Tycho Andersen
2026-05-18 22:26 ` Alejandro Colomar
2026-05-18 3:13 ` [PATCH v2 0/2] Document seccomp flags funsafemath
2026-05-18 22:15 ` Alejandro Colomar
2026-05-18 3:14 ` [PATCH v2 1/2] man/man2/seccomp.2: Document SECCOMP_FILTER_FLAG_TSYNC_ESRCH funsafemath
2026-05-18 3:15 ` [PATCH v2 2/2] man/man2/seccomp.2: Document SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV funsafemath
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=agjag_tIzuKpME-B@devuan \
--to=alx@kernel.org \
--cc=funsafemath@proton.me \
--cc=linux-man@vger.kernel.org \
--cc=tycho@tycho.ws \
/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