gfs2: Handle -EBUSY result of insert_inode_locked4
authorAndreas Gruenbacher <agruenba@redhat.com>
Sat, 5 Nov 2022 16:12:34 +0000 (17:12 +0100)
committerAndreas Gruenbacher <agruenba@redhat.com>
Mon, 5 Dec 2022 21:21:23 +0000 (22:21 +0100)
commit4ec3c19d058f7391ec631b8a1b0a690422b246a9
tree63daf90428b577c90b1e17dbcdf087ce8fb8b319
parent38552ff676f072e7d15c5e0a877fda613e57ed2d
gfs2: Handle -EBUSY result of insert_inode_locked4

When creating a new inode, there is a small chance that an inode lookup
for a previous version of the same inode is still in progress.  In that
case, that previous lookup will eventually fail, but we may still need
to retry here.

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