aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason A. Harmening <jah@FreeBSD.org>2023-01-16 21:48:11 +0000
committerJason A. Harmening <jah@FreeBSD.org>2023-04-18 01:31:40 +0000
commita5d82b55fe76307df5277caa4bb1b7963a405e34 (patch)
tree408ae4529b688753944e4f8329ca7a8a7af92783
parenta18c403fbddb0fa9650f133a026f40ad33751134 (diff)
downloadsrc-a5d82b55fe76307df5277caa4bb1b7963a405e34.tar.gz
src-a5d82b55fe76307df5277caa4bb1b7963a405e34.zip
Remove an impossible condition from unionfs_lock()
We hold the vnode interlock, so vnode private data cannot suddenly become NULL. Tested by: pho Reviewed by: kib, markj Differential Revision: https://reviews.freebsd.org/D39272
-rw-r--r--sys/fs/unionfs/union_vnops.c8
1 files changed, 0 insertions, 8 deletions
diff --git a/sys/fs/unionfs/union_vnops.c b/sys/fs/unionfs/union_vnops.c
index f78e653280a4..a0ff5c140e82 100644
--- a/sys/fs/unionfs/union_vnops.c
+++ b/sys/fs/unionfs/union_vnops.c
@@ -1982,14 +1982,6 @@ unionfs_lock(struct vop_lock1_args *ap)
vholdnz(uvp);
uhold = 1;
VOP_UNLOCK(uvp);
- unp = VTOUNIONFS(vp);
- if (unp == NULL) {
- /* vnode is released. */
- VI_UNLOCK(vp);
- VOP_UNLOCK(lvp);
- vdrop(uvp);
- return (EBUSY);
- }
}
VI_LOCK_FLAGS(lvp, MTX_DUPOK);
flags |= LK_INTERLOCK;