git: 974efbb3d5c0 - main - unionfs: fix typo in comment
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 10 Feb 2022 21:09:47 UTC
The branch main has been updated by jah:
URL: https://cgit.FreeBSD.org/src/commit/?id=974efbb3d5c0a21062e67cd72b6685acaaf17fdd
commit 974efbb3d5c0a21062e67cd72b6685acaaf17fdd
Author: Jason A. Harmening <jah@FreeBSD.org>
AuthorDate: 2022-02-10 21:14:11 +0000
Commit: Jason A. Harmening <jah@FreeBSD.org>
CommitDate: 2022-02-10 21:17:43 +0000
unionfs: fix typo in comment
I deleted the wrong word when writing up a comment in a prior change;
the covered vnode may be recursed during any unmount, not just forced
unmount.
---
sys/fs/unionfs/union_subr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys/fs/unionfs/union_subr.c b/sys/fs/unionfs/union_subr.c
index 466c88c705f4..08202501fe02 100644
--- a/sys/fs/unionfs/union_subr.c
+++ b/sys/fs/unionfs/union_subr.c
@@ -443,7 +443,7 @@ unionfs_noderem(struct vnode *vp)
int writerefs;
/*
- * The root vnode lock may be recursed during forcible, because
+ * The root vnode lock may be recursed during unmount, because
* it may share the same lock as the unionfs mount's covered vnode,
* which is locked across VFS_UNMOUNT(). This lock will then be
* recursively taken during the vflush() issued by unionfs_unmount().