src-test2/sys/miscfs/nullfs, branch release/3.2.0_cvs

This commit was manufactured by cvs2svn to create tag

1999-05-24T16:47:10Z

'RELENG_3_2_0_RELEASE'. This commit was manufactured to restore the state of the 3.2-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

The "easy" fixes for compiling the kernel -Wunused: remove unreferenced static

1998-12-07T21:58:50Z

and local variables, goto labels, and functions declared but not defined.

Removed statically configured mount type numbers (MOUNT_*) and all

1998-09-07T13:17:06Z

references to them. The change a couple of days ago to ignore these numbers in statically configured vfsconf structs was slightly premature because the cd9660, cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number in their vfsconf struct.

Fixed printf format errors.

1998-07-30T17:40:45Z

Cast pointers to uintptr_t/intptr_t instead of to u_long/long,

1998-07-15T02:32:35Z

respectively. Most of the longs should probably have been u_longs, but this changes is just to prevent warnings about casts between pointers and integers of different sizes, not to fix poorly chosen types.

VOP_STRATEGY grows an (struct vnode *) argument

1998-07-04T20:45:42Z

as the value in b_vp is often not really what you want. (and needs to be frobbed). more cleanups will follow this. Reviewed by: Bruce Evans

Don't silently accept attempts to change flags where they are not

1998-06-10T06:34:57Z

supported.

As described by the submitter:

1998-05-06T05:29:41Z

Reverse the VFS_VRELE patch. Reference counting of vnodes does not need to be done per-fs. I noticed this while fixing vfs layering violations. Doing reference counting in generic code is also the preference cited by John Heidemann in recent discussions with him. The implementation of alternative vnode management per-fs is still a valid requirement for some filesystems but will be revisited sometime later, most likely using a different framework. Submitted by: Michael Hancock

Seventy-odd "its" / "it's" typos in comments fixed as per kern/6108.

1998-04-17T22:37:19Z

The intent is to get rid of WILLRELE in vnode_if.src by making

1998-03-01T22:46:53Z

a complement to all ops that return a vpp, VFS_VRELE. This is initially only for file systems that implement the following ops that do a WILLRELE: vop_create, vop_whiteout, vop_mknod, vop_remove, vop_link, vop_rename, vop_mkdir, vop_rmdir, vop_symlink This is initial DNA that doesn't do anything yet. VFS_VRELE is implemented but not called. A default vfs_vrele was created for fs implementations that use the standard vnode management routines. VFS_VRELE implementations were made for the following file systems: Standard (vfs_vrele) ffs mfs nfs msdosfs devfs ext2fs Custom union umapfs Just EOPNOTSUPP fdesc procfs kernfs portal cd9660 These implementations may change as VOP changes are implemented. In the next phase, in the vop implementations calls to vrele and the vrele part of vput will be moved to the top layer vfs_vnops and made visible to all layers. vput will be replaced by unlock in these cases. Unlocking will still be done in the per fs layer but the refcount decrement will be triggered at the top because it doesn't hurt to hold a vnode reference a little longer. This will have minimal impact on the structure of the existing code. This will only be done for vnode arguments that are released by the various fs vop implementations. Wider use of VFS_VRELE will likely require restructuring of the code. Reviewed by: phk, dyson, terry et. al. Submitted by: Michael Hancock