<dec f='src/src/sys/fs/msdosfs/denode.h' l='272' type='int msdosfs_lookup(void * )'/>
<doc f='src/src/sys/fs/msdosfs/denode.h' l='269'>/*
 * Prototypes for MSDOSFS vnode operations
 */</doc>
<def f='src/src/sys/fs/msdosfs/msdosfs_lookup.c' l='95' ll='540' type='int msdosfs_lookup(void * v)'/>
<doc f='src/src/sys/fs/msdosfs/msdosfs_lookup.c' l='80'>/*
 * When we search a directory the blocks containing directory entries are
 * read and examined.  The directory entries contain information that would
 * normally be in the inode of a unix filesystem.  This means that some of
 * a directory&apos;s contents may also be in memory resident denodes (sort of
 * an inode).  This can cause problems if we are searching while some other
 * process is modifying a directory.  To prevent one process from accessing
 * incompletely modified directory information we depend upon being the
 * sole owner of a directory block.  bread/brelse provide this service.
 * This being the case, when a process modifies a directory it must first
 * acquire the disk block that contains the directory entry to be modified.
 * Then update the disk block and the denode, and then write the disk block
 * out to disk.  This way disk blocks containing directory entries and in
 * memory denode&apos;s will be in synch.
 */</doc>
<use f='src/src/sys/fs/msdosfs/msdosfs_vnops.c' l='1881'/>
<use f='src/src/sys/fs/msdosfs/msdosfs_vnops.c' l='1881'/>
<use f='src/src/sys/fs/msdosfs/msdosfs_vnops.c' l='1881'/>
<use f='src/src/sys/fs/msdosfs/msdosfs_vnops.c' l='1881'/>
