Messages in this thread | | | Subject | Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between | From | David Woodhouse <> | Date | Wed, 04 May 2005 22:35:07 +0100 |
| |
On Wed, 2005-05-04 at 13:04 -0700, Andrew Morton wrote: > This sounds more like a bug in the iget() caller to me. > > Question is: if the inode has zero refcount and is unhashed then how > did the caller get its sticky paws onto the inode* in the first place? > > If the caller had saved a copy of the inode* in local storage then the > caller should have taken a ref against the inode. > > If the caller had just looked up the inode via hastable lookup via > iget_whatever() then again the caller will have a ref on the inode. > > So. Please tell us more about how the caller got into this situation.
I could explain in detail how JFFS2 garbage collection works, moving log entries out of the way by calling iget() on the inode to which they belong.... or I could just say "NFS".
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |