[lkml]   [2005]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
    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".


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-05-04 23:47    [W:0.021 / U:76.936 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site