From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH] man/man2/sigaction.2: Update si_code list with Linux v6.16
Date: Tue, 09 Sep 2025 00:13:36 -0300 [thread overview]
Message-ID: <87plc071y7.fsf@linaro.org> (raw)
In-Reply-To: <1131d940-b487-4ce4-8316-533cffbdc173@redhat.com> (Carlos O'Donell's message of "Wed, 3 Sep 2025 11:37:31 -0400")
Carlos O'Donell <carlos@redhat.com> writes:
> On 9/2/25 11:08 PM, Thiago Jung Bauermann wrote:
>> To be honest, my motivation to write this patch was just to fix the fact
>> that SEGV_CPERR was not mentioned. Then I noticed that other constants
>> were missing too, and thought it would be easy enough to add them as
>> well...
>
> Welcome to the rabbit hole! :-)
Thanks? :-)
>>> (a) Adding the constants to C libraries in a conformant way.
>>>
>>> (b) Cleaning up the UAPI header to be conforming and work with
>>> the existing C libraries to include it indirectly.
>>>
>>> (c) Cleaning up both headers to allow dual inclusion with
>>> additional constants showing up as needed.
>>>
>>> In summary:
>>>
>>> - This patch contains 2 constants that don't work today in a glibc-based
>>> userspace.
>>>
>>> - The existing man page documents 1 constants that doesn't work today
>>> with the standard #include <signal.h>.
>> As you suggested (thanks!), I sent a patch to the glibc mailing list
>> adding the si_codes it's missing to its siginfo-conts.h header:
>> https://inbox.sourceware.org/libc-alpha/20250903024151.3030839-1-thiago.bauermann@linaro.org/
>> If that one is accepted, hopefully this patch can go in?
>
> Yes, that works for me.
Just FYI to the people on this mailing list, the glibc patch was
committed today.
--
Thiago
next prev parent reply other threads:[~2025-09-09 3:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 21:07 [PATCH] man/man2/sigaction.2: Update si_code list with Linux v6.16 Thiago Jung Bauermann
2025-08-29 11:56 ` Carlos O'Donell
2025-09-03 3:08 ` Thiago Jung Bauermann
2025-09-03 15:37 ` Carlos O'Donell
2025-09-09 3:13 ` Thiago Jung Bauermann [this message]
2025-09-09 6:32 ` Alejandro Colomar
2025-09-09 18:26 ` Carlos O'Donell
2025-09-09 18:58 ` Alejandro Colomar
2025-09-09 19:15 ` Thiago Jung Bauermann
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=87plc071y7.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=alx@kernel.org \
--cc=carlos@redhat.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