[Bug nscd/19733] nscd_certainly_running flag mechanism broken on nscd shared cache

fweimer at redhat dot com sourceware-bugzilla@sourceware.org
Thu Jun 6 08:16:57 GMT 2024


https://sourceware.org/bugzilla/show_bug.cgi?id=19733

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|MOVED                       |---

--- Comment #7 from Florian Weimer <fweimer at redhat dot com> ---
I think the flag states are just unfortunate.  The value 0 should mean
“definitely not running”, not “please make a timestamp check”.

Using the timestamp field is hard because it's currently 64 bit, and the kernel
will only zap 32 bits for us.

Alternatively, we can use the system service manager to invalidate the mappings
from the outside, with a new --offline-invalidate option to nscd. This can
overwrite both timestamp and nscd_certainly_running with zeros. It has the
advantage that it does not need updates to client code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Glibc-bugs mailing list