gfs2: Don't call cancel_delayed_work_sync from within delete work function
authorAndreas Gruenbacher <agruenba@redhat.com>
Mon, 2 Nov 2020 20:11:30 +0000 (21:11 +0100)
committerAndreas Gruenbacher <agruenba@redhat.com>
Mon, 2 Nov 2020 20:34:47 +0000 (21:34 +0100)
commit6bd1c7bd4ee7b17980cdc347522dcb76feac9b98
treedbdd59dc08b716d982bf5df2be9f8ef04abd963c
parentc5c68724696e7d2f8db58a5fce3673208d35c485
gfs2: Don't call cancel_delayed_work_sync from within delete work function

Right now, we can end up calling cancel_delayed_work_sync from within
delete_work_func via gfs2_lookup_by_inum -> gfs2_inode_lookup ->
gfs2_cancel_delete_work.  When that happens, it will result in a
deadlock.  Instead, gfs2_inode_lookup should skip the call to
gfs2_cancel_delete_work when called from delete_work_func (blktype ==
GFS2_BLKST_UNLINKED).

Reported-by: Alexander Ahring Oder Aring <aahringo@redhat.com>
Fixes: a0e3cc65fa29 ("gfs2: Turn gl_delete into a delayed work")
Cc: stable@vger.kernel.org # v5.8+
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
fs/gfs2/inode.c