From d5f342f2daa0632a7ce5dc14cc5bc84bea1b8a16 Mon Sep 17 00:00:00 2001 From: kib Date: Tue, 13 Apr 2010 08:45:55 +0000 Subject: Remove XXX comment. Add another comment, describing why f_vnode assignment is useful. MFC after: 3 days --- sys/kern/vfs_syscalls.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'sys/kern') diff --git a/sys/kern/vfs_syscalls.c b/sys/kern/vfs_syscalls.c index c329adc..f266688 100644 --- a/sys/kern/vfs_syscalls.c +++ b/sys/kern/vfs_syscalls.c @@ -1124,7 +1124,12 @@ kern_openat(struct thread *td, int fd, char *path, enum uio_seg pathseg, NDFREE(&nd, NDF_ONLY_PNBUF); vp = nd.ni_vp; - fp->f_vnode = vp; /* XXX Does devfs need this? */ + /* + * Store the vnode, for any f_type. Typically, the vnode use + * count is decremented by direct call to vn_closefile() for + * files that switched type in the cdevsw fdopen() method. + */ + fp->f_vnode = vp; /* * If the file wasn't claimed by devfs bind it to the normal * vnode operations here. -- cgit v1.1