gfs2: Clean up after gfs2_create_inode rework
authorAndreas Gruenbacher <agruenba@redhat.com>
Sun, 4 Dec 2022 02:48:52 +0000 (03:48 +0100)
committerAndreas Gruenbacher <agruenba@redhat.com>
Tue, 6 Dec 2022 15:06:31 +0000 (16:06 +0100)
commit764665c6775251d4569ba9f09981459bbb166359
treeccb4f9c1205c20dfb6d37463c2b97a7e58433ae0
parent97236ad5a68c6b7603cea2ad01c588887e5cb961
gfs2: Clean up after gfs2_create_inode rework

Since commit 3d36e57ff768 ("gfs2: gfs2_create_inode rework"),
gfs2_evict_inode() and gfs2_create_inode() / gfs2_inode_lookup() will
synchronize via the inode hash table and we can be certain that once a
new inode is inserted into the inode hash table(), gfs2_evict_inode()
has completely destroyed any previous versions.  We no longer need to
worry about overlapping inode object lifespans.  Update the code and
comments accordingly.

Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
fs/gfs2/glock.h
fs/gfs2/super.c