From: Alejandro Colomar <alx@kernel.org>
To: ChaseKnowlden <haroldknowlden@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/seccomp.2: Fix signal.h type conflict with glibc in seccomp.2
Date: Thu, 21 May 2026 01:10:05 +0200 [thread overview]
Message-ID: <ag4-lKqvpieapYrt@devuan> (raw)
In-Reply-To: <20260520213258.23500-1-haroldknowlden@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Hi ChaseKnowlden,
> Subject: Re: [PATCH] man/man2/seccomp.2: Fix signal.h type conflict with glibc in seccomp.2
On 2026-05-20T17:32:58-0400, ChaseKnowlden wrote:
> Signed-off-by: ChaseKnowlden <haroldknowlden@gmail.com>
You should say something more in the commit message. What type conflict
do you have? Why is this fix correct? It would be good to link to
other sources that confirm this, and/or CC glibc.
> ---
> man/man2/seccomp.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man/man2/seccomp.2 b/man/man2/seccomp.2
> index e469f3997..8b8f2fc61 100644
> --- a/man/man2/seccomp.2
> +++ b/man/man2/seccomp.2
> @@ -16,7 +16,7 @@ Standard C library
> .BR "#include <linux/seccomp.h>" " /* Definition of " SECCOMP_* " constants */"
> .BR "#include <linux/filter.h>" " /* Definition of " "struct sock_fprog" " */"
> .BR "#include <linux/audit.h>" " /* Definition of " AUDIT_* " constants */"
> -.BR "#include <linux/signal.h>" " /* Definition of " SIG* " constants */"
> +.BR "#include <signal.h>" " /* Definition of " SIG* " constants */"
Please keep the alignment of the comments.
Have a lovely night!
Alex
> .BR "#include <sys/ptrace.h>" " /* Definition of " PTRACE_* " constants */"
> .\" Kees Cook noted: Anything that uses SECCOMP_RET_TRACE returns will
> .\" need <sys/ptrace.h>
> --
> 2.54.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-05-20 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 21:32 [PATCH] man/man2/seccomp.2: Fix signal.h type conflict with glibc in seccomp.2 ChaseKnowlden
2026-05-20 23:10 ` Alejandro Colomar [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=ag4-lKqvpieapYrt@devuan \
--to=alx@kernel.org \
--cc=haroldknowlden@gmail.com \
--cc=linux-man@vger.kernel.org \
/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