This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nscd/19733] nscd_certainly_running flag mechanism broken on nscd shared cache
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 10 Mar 2016 20:21:13 +0000
- Subject: [Bug nscd/19733] nscd_certainly_running flag mechanism broken on nscd shared cache
- Auto-submitted: auto-generated
- References: <bug-19733-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19733
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
Flags| |security-
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
We could piggy-back on the robust mutex processing on Linux.
I have not tested if the current implementation supports this, but it might be
possible to have a permanently-locked mutex, and check that it is locked using
pthread_mutex_trylock. If this function returns EOWNERDEAD, the mapping is
stale. If it returns EBUSY, the mapping is live.
(Marking as security-, even though this could lead to stale data being used.)
--
You are receiving this mail because:
You are on the CC list for the bug.