OSDN Git Service

gfs2: When gfs2_dirty_inode gets a glock error, dump the glock
authorBob Peterson <rpeterso@redhat.com>
Thu, 30 Jul 2020 17:31:38 +0000 (12:31 -0500)
committerAndreas Gruenbacher <agruenba@redhat.com>
Fri, 7 Aug 2020 15:26:24 +0000 (17:26 +0200)
commite28c02b94f9e039beeb5c75198caf6e17b66c520
tree44913d7018232c7ab46bf499801667499e74f45b
parent70499cdfeb3625c87eebe4f7a7ea06fa7447e5df
gfs2: When gfs2_dirty_inode gets a glock error, dump the glock

Before this patch, if function gfs2_dirty_inode got an error when
trying to lock the inode glock, it complained, but it didn't say
what glock or inode had the problem.

In this case, it almost always means that dinode_in found an error
with the dinode in the file system. So it makes sense to dump the
glock, which tells us the location of the dinode in the file system.
That will allow us to analyze the corruption from the metadata.

Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
fs/gfs2/super.c