gfs2: Keep track of deleted inode generations in LVBs
authorAndreas Gruenbacher <agruenba@redhat.com>
Mon, 13 Jan 2020 20:21:49 +0000 (21:21 +0100)
committerAndreas Gruenbacher <agruenba@redhat.com>
Fri, 5 Jun 2020 18:19:20 +0000 (20:19 +0200)
commitf286d627ef026a4d04b41ae5917d58ddf243c3c5
treefac5959649e646e708c3d6412c984cc86d10221a
parent15f2547b4157a1e7e4d75bec5df097c1436f6cbd
gfs2: Keep track of deleted inode generations in LVBs

When deleting an inode, keep track of the generation of the deleted inode in
the inode glock Lock Value Block (LVB).  When trying to delete an inode
remotely, check the last-known inode generation against the deleted inode
generation to skip duplicate remote deletes.  This avoids taking the resource
group glock in order to verify the block type.

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