[Bug libc/24882] login: pututline uses potentially outdated cache
cvs-commit at gcc dot gnu.org
sourceware-bugzilla@sourceware.org
Fri Jan 17 14:02:00 GMT 2020
https://sourceware.org/bugzilla/show_bug.cgi?id=24882
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.30/master branch has been updated by Florian Weimer
<fw@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=83f793e6a63c4bdd1b2f39618040a8317562a1f7
commit 83f793e6a63c4bdd1b2f39618040a8317562a1f7
Author: Florian Weimer <fweimer@redhat.com>
Date: Thu Nov 7 18:15:18 2019 +0100
login: Acquire write lock early in pututline [BZ #24882]
It has been reported that due to lack of fairness in POSIX file
locking, the current reader-to-writer lock upgrade can result in
lack of forward progress. Acquiring the write lock directly
hopefully avoids this issue if there are only writers.
This also fixes bug 24882 due to the cache revalidation in
__libc_pututline.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Change-Id: I57e31ae30719e609a53505a0924dda101d46372e
(cherry picked from commit be6b16d975683e6cca57852cd4cfe715b2a9d8b1)
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Glibc-bugs
mailing list