git: 6b4523011723 - main - unionfs_noderem(): fix typo

Jason A. Harmening <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.src
Message-ID <6a88fc33.32442.dff23e8__21801.6696207755$1787362386$gmane$org@gitrepo.freebsd.org>
The branch main has been updated by jah:

URL: https://cgit.FreeBSD.org/src/commit/?id=6b452301172391815c6e21a9875f75c8ddb35735

commit 6b452301172391815c6e21a9875f75c8ddb35735
Author:     Jason A. Harmening <[email protected]>
AuthorDate: 2026-08-15 16:16:09 +0000
Commit:     Jason A. Harmening <[email protected]>
CommitDate: 2026-08-22 01:32:15 +0000

    unionfs_noderem(): fix typo
    
    Reviewed by:            kib, markj
    Differential Revision:  https://reviews.freebsd.org/D58858
---
 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 6489eb77ce2b..3254808fd490 100644
--- a/sys/fs/unionfs/union_subr.c
+++ b/sys/fs/unionfs/union_subr.c
@@ -491,7 +491,7 @@ unionfs_noderem(struct vnode *vp)
 	 * to synchronize against any unionfs_lock() operation which may still
 	 * hold the lower vnode lock.  We do not need to do this for the root
 	 * vnode, as the root vnode should always have both upper and lower
-	 * base vnodes for its entire lifecycled, so unionfs_lock() should
+	 * base vnodes for its entire lifecycle, so unionfs_lock() should
 	 * never attempt to lock its lower vnode in the first place.
 	 * Moreover, during unmount of a non-"below" unionfs mount, the lower
 	 * root vnode will already be locked as it is the covered vnode.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.