GFS2: Don't do glock put on when inode creation fails
authorBob Peterson <rpeterso@redhat.com>
Fri, 4 Dec 2015 19:04:34 +0000 (13:04 -0600)
committerBob Peterson <rpeterso@redhat.com>
Fri, 18 Dec 2015 17:04:46 +0000 (11:04 -0600)
commit6cc4b6e801c725321e9f63ca7c2d00af8df24699
tree9753131b4c37ac330f5398a82fc46a6ac537c95e
parent5ea31bc0a6524b4fee8dc9ae8005d4a114a79812
GFS2: Don't do glock put on when inode creation fails

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: Bob Peterson <rpeterso@redhat.com>
fs/gfs2/inode.c