On Tue, Dec 03, 2013 at 05:59:38AM -0500, Jeff Layton wrote: > > Actually, it's pretty unlikely that this would get pruned here. > lru_put_end updates the timestamp on the entry, so the > prune_cache_entries run would have to take more than 120s and prune > everything off of the list. > > The real bug is that we can later find the entry in the hash that we > intend to reuse and then free that cache entry. The safe thing to do > here is to just unhash the entry that we intend to use so that it can't > be found or pruned. > > I sent a patch that should fix this the correct way: > > [PATCH] nfsd: when reusing an existing repcache entry, unhash it first > Yes, you are right. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
