• B
    GFS2: Don't do glock put on when inode creation fails · 6cc4b6e8
    Bob Peterson 提交于
    Currently the error path of function gfs2_inode_lookup calls function
    gfs2_glock_put corresponding to an earlier call to gfs2_glock_get for
    the inode glock. That's wrong because the error path also calls
    iget_failed() which eventually calls iput, which eventually calls
    gfs2_evict_inode, which does another gfs2_glock_put. This double-put
    can cause the glock reference count to get off.
    Signed-off-by: NBob Peterson <rpeterso@redhat.com>
    6cc4b6e8
inode.c 49.2 KB