This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Update to new generic semaphore algorithm v2
On 2/7/19 12:15 PM, Florian Weimer wrote:
> * Andreas Schwab:
>> On Feb 07 2019, Florian Weimer <firstname.lastname@example.org> wrote:
>>> Hasn't this been reported before?
>> Any pointer?
> I found <https://sourceware.org/bugzilla/show_bug.cgi?id=17980>.
One of two scenarios are possible. It either worked by accident
or it it was intentional but nobody bothered to document it in
the implementation sources e.g. comment explaining the compatible
Either way I don't suggest we support mixed 32-bit and 64-bit
uses like this.
Speaking of which, how is a 32-bit process supposed to lock the
64-bit nscd data for reading with *FD* shared mappings where
the client does the work? Ah, it looks like a 32-bit int is
explicitly used with atomic ops for locking. So no semaphore,
or anything else.