summaryrefslogtreecommitdiffstats
path: root/sys/fs
diff options
context:
space:
mode:
authored <ed@FreeBSD.org>2008-09-11 20:15:34 +0000
committered <ed@FreeBSD.org>2008-09-11 20:15:34 +0000
commit8cc770d042cd8fffb166d2ee65abffe944e7ee7d (patch)
tree1d5f461be15066482c33debd227f24e8e5b915fa /sys/fs
parent8470014e066e692ff386ba173ea115403139b076 (diff)
downloadFreeBSD-src-8cc770d042cd8fffb166d2ee65abffe944e7ee7d.zip
FreeBSD-src-8cc770d042cd8fffb166d2ee65abffe944e7ee7d.tar.gz
Fix two small typo's in comments in the nullfs vnops code.
Submitted by: Jille Timmermans <jille quis cx>
Diffstat (limited to 'sys/fs')
-rw-r--r--sys/fs/nullfs/null_vnops.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/fs/nullfs/null_vnops.c b/sys/fs/nullfs/null_vnops.c
index ca7ed0c..4a41396 100644
--- a/sys/fs/nullfs/null_vnops.c
+++ b/sys/fs/nullfs/null_vnops.c
@@ -625,7 +625,7 @@ null_islocked(struct vop_islocked_args *ap)
/*
* There is no way to tell that someone issued remove/rmdir operation
- * on the underlying filesystem. For now we just have to release lowevrp
+ * on the underlying filesystem. For now we just have to release lowervp
* as soon as possible.
*
* Note, we can't release any resources nor remove vnode from hash before
@@ -676,7 +676,7 @@ null_reclaim(struct vop_reclaim_args *ap)
lockmgr(vp->v_vnlock, LK_EXCLUSIVE | LK_INTERLOCK, VI_MTX(vp));
vput(lowervp);
} else
- panic("null_reclaim: reclaiming an node with now lowervp");
+ panic("null_reclaim: reclaiming a node with no lowervp");
FREE(xp, M_NULLFSNODE);
return (0);
OpenPOWER on IntegriCloud