On Sat, May 16, 2015 at 7:45 PM, Ivan Zhakov <[email protected]> wrote:
> On 16 May 2015 at 07:48, Stefan Fuhrmann <[email protected]> > wrote: > > On Fri, May 15, 2015 at 7:25 PM, Philip Martin < > [email protected]> > > wrote: > >> Another issue: find_entry() now calls drop_entry() in more cases and can > >> now call it when find_empty==FALSE during read operations. On Unix when > >> using the read-write lock this means the cache gets modified while only > >> holding a read lock, not a write lock, and that can corrupt the cache. > >> > As far I understand find_entry(find_empty == TRUE) requires write-lock > for cache, while only read-lock is required for find_empty == FALSE. > Is correct? It would be nice to document this in docstring. > Done in r1679866. -- Stefan^2.
