[Bug nscd/13931] New: Reload nscd cache entry even if its timeout is equal to the current time

siddhesh at redhat dot com sourceware-bugzilla@sourceware.org
Fri Mar 30 11:10:00 GMT 2012


http://sourceware.org/bugzilla/show_bug.cgi?id=13931

             Bug #: 13931
           Summary: Reload nscd cache entry even if its timeout is equal
                    to the current time
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nscd
        AssignedTo: unassigned@sourceware.org
        ReportedBy: siddhesh@redhat.com
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


With the current implementation of cache expiry, the timer for expiry
is set exactly at the timeout value of an entry. As a result, there is often a
case where the cache prune is called at exactly the timeout time, causing the
prune_cache code to think that the timeout has not occurred yet. As a result,
the entry is not invalidated or reloaded until the next prune cycle, which is
at least 15 seconds away. Fix is to mark an entry as timed out even when the
time that prune_cache is called is exactly equal to the timeout time of the
entry.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the Glibc-bugs mailing list