[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260724214156.GC27423@brightrain.aerifal.cx>
Date: Fri, 24 Jul 2026 17:41:57 -0400
From: Rich Felker <dalias@...c.org>
To: Jake Adamson <jakeadamson@...gle.com>
Cc: enh <enh@...gle.com>, musl@...ts.openwall.com,
Nick Desaulniers <ndesaulniers@...gle.com>,
Peter Oskolkov <posk@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
mathieu.desnoyers@...icios.com
Subject: Re: Re: Question: number of arguments of musl's membarrier
does not match Linux syscall
On Fri, Jul 24, 2026 at 10:40:38AM -0700, Jake Adamson wrote:
> For a short term solution would it make scene to just check if
> MEMBARRIER_CMD_FLAG_CPU cmd
> has been passed in, return -1 and set errno to EINVAL or what ever is
> the appropriate value?
> That way you don't have remove MEMBARRIER_CMD_FLAG_CPU and change the header?
The problem is caught at compile-time; I don't see a reason to check
this at runtime.
The problem I was trying to address is that the presence of
MEMBARRIER_CMD_FLAG_CPU in the header causes applications to think the
3-argument form is available when there's actually no way to use it.
But maybe even without it programs will be assuming the glibc
signature and passing a third unused argument..?
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.
