Bob Peterson 6cc4b6e801 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>
2015-12-18 11:04:46 -06:00
..
2014-03-19 15:16:24 +00:00
2014-03-03 13:50:12 +00:00
2015-12-14 12:19:37 -06:00
2015-12-14 12:19:24 -06:00
2015-12-14 12:19:24 -06:00
2015-10-29 12:57:48 -05:00
2015-12-14 12:19:37 -06:00
2013-06-14 11:17:15 +01:00
2013-06-03 14:20:18 -07:00
2015-11-09 15:11:24 -08:00
2014-05-14 10:04:34 +01:00
2015-09-11 12:23:51 -07:00
2011-05-10 13:12:49 +01:00
2015-11-16 12:00:29 -06:00
2015-12-14 12:19:37 -06:00
2015-12-14 12:19:24 -06:00
2015-01-13 10:48:57 +00:00
2015-05-05 13:23:22 -05:00
2012-01-11 09:23:05 +00:00
2015-11-16 12:00:29 -06:00
2009-12-16 12:16:49 -05:00