gfs2: Stop using rhashtable_walk_peek
authorAndreas Gruenbacher <agruenba@redhat.com>
Wed, 28 Mar 2018 10:05:35 +0000 (12:05 +0200)
committerBob Peterson <rpeterso@redhat.com>
Thu, 12 Apr 2018 16:41:19 +0000 (09:41 -0700)
commit3fd5d3ad35dc44aaf0f28d60cc0eb75887bff54d
treee94c5e90a62de825fe65c34093109d4ec40639e6
parent450b1f6f56350c630e795f240dc5a77aa8aa2419
gfs2: Stop using rhashtable_walk_peek

Function rhashtable_walk_peek is problematic because there is no
guarantee that the glock previously returned still exists; when that key
is deleted, rhashtable_walk_peek can end up returning a different key,
which will cause an inconsistent glock dump.  Fix this by keeping track
of the current glock in the seq file iterator functions instead.

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