[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250612172125.GU1827@brightrain.aerifal.cx>
Date: Thu, 12 Jun 2025 13:21:26 -0400
From: Rich Felker <dalias@...c.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: enh <enh@...gle.com>, musl@...ts.openwall.com,
Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: sys/prctl.h differences vs man page
On Thu, Jun 12, 2025 at 06:50:00PM +0200, Sebastian Andrzej Siewior wrote:
> On 2025-06-12 12:34:08 [-0400], Rich Felker wrote:
> > On Thu, Jun 12, 2025 at 12:28:24PM -0400, enh wrote:
> > > https://man7.org/linux/man-pages/man2/prctl.2.html
> >
> > OK, apparently this is either a regression since the man-pages 6.8-r0
> > package I have here on Alpine, or an old version. Guess we should look
> > at the git history and how that happened...
>
> That would be commit
> ae31bd15b65ce ("prctl.2, PR_*.2const: SYNOPSIS: #include <linux/prctl.h> for the PR_* constants")
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=ae31bd15b65ce
>
> Commit is present since man-pages-6.9.
Yes, that looks completely unmotivated and should be reverted.
In general, you should never include both the linux uapi and
userspace/libc header for the same thing.
If your libc delegates to the linux uapi header, it will already have
included it implicitly to get the definitions.
If not, the two conflict.
And abstractly: one is describing the application-to-libc-function
interface, the other is describing the raw syscall interface. You
include the header for which one you're using.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
