Re: [PATCH] bugfix: two read_inode() calls without clear_inode() call between

> Could you please explain me, why we need to wake up somebody right > before freeing an inode? It seems for me, if somebody really wait on > this inode, then they have a good chance to access already freed memory. find_inode() needs to be woken up (__wait_on_freeing_inode) when an inode being f

Re: [PATCH] bugfix: two read_inode() calls without clear_inode() call between

Hello, Could you please explain me, why we need to wake up somebody right before freeing an inode? It seems for me, if somebody really wait on this inode, then they have a good chance to access already freed memory. Thank you, Vasily Averin diff --git a/fs/inode.c b/fs/inode.c --- a