From d7c11454f871e56ead7e86b39cfa450f54ae87dc Mon Sep 17 00:00:00 2001 From: Igor Ostapenko Date: Mon, 8 May 2023 19:19:34 +0300 Subject: [PATCH] vfs: fix description comment of vfs_lookup() Signed-off-by: Igor Ostapenko --- sys/kern/vfs_lookup.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sys/kern/vfs_lookup.c b/sys/kern/vfs_lookup.c index a75ea4ca16d65e..9e98d2fa3afda6 100644 --- a/sys/kern/vfs_lookup.c +++ b/sys/kern/vfs_lookup.c @@ -840,7 +840,7 @@ vfs_lookup_failifexists(struct nameidata *ndp) * Search a pathname. * This is a very central and rather complicated routine. * - * The pathname is pointed to by ni_ptr and is of length ni_pathlen. + * The pathname is pointed to by cn_nameptr and is of length ni_pathlen. * The starting directory is taken from ni_startdir. The pathname is * descended until done, or a symbolic link is encountered. The variable * ni_more is clear if the path is completed; it is set to one if a @@ -861,7 +861,7 @@ vfs_lookup_failifexists(struct nameidata *ndp) * Overall outline of lookup: * * dirloop: - * identify next component of name at ndp->ni_ptr + * identify next component of name at ndp->ni_cnd->cn_nameptr * handle degenerate case where name is null string * if .. and crossing mount points and on mounted filesys, find parent * call VOP_LOOKUP routine for next component name