sunrpc/cache: ensure items removed from cache do not have pending upcalls.
It is possible for a race to set CACHE_PENDING after cache_clean() has removed a cache entry from the cache. If CACHE_PENDING is still set when the entry is finally 'put', the cache_dequeue() will never happen and we can leak memory. So set a new flag 'CACHE_CLEANED' when we remove something from the cache, and don't queue any upcall if it is set. If CACHE_PENDING is set before CACHE_CLEANED, the call that cache_clean() makes to cache_fresh_unlocked() will free memory as needed. If CACHE_PENDING is set after CACHE_CLEANED, the test in sunrpc_cache_pipe_upcall will ensure that the memory is not allocated. Reported-by: <bstroesser@ts.fujitsu.com> Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
This commit is contained in:

committed by
J. Bruce Fields

parent
2a1c7f53fd
commit
013920eb5d
@@ -57,6 +57,7 @@ struct cache_head {
|
||||
#define CACHE_VALID 0 /* Entry contains valid data */
|
||||
#define CACHE_NEGATIVE 1 /* Negative entry - there is no match for the key */
|
||||
#define CACHE_PENDING 2 /* An upcall has been sent but no reply received yet*/
|
||||
#define CACHE_CLEANED 3 /* Entry has been cleaned from cache */
|
||||
|
||||
#define CACHE_NEW_EXPIRY 120 /* keep new things pending confirmation for 120 seconds */
|
||||
|
||||
|
Reference in New Issue
Block a user