src/sys/kern/vnode_if.src, branch release/6.0.0_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F6.0.0_cvs 2005-11-03T00:35:26Z This commit was manufactured by cvs2svn to create tag 2005-11-03T00:35:26Z cvs2svn cvs2svn@FreeBSD.org 2005-11-03T00:35:26Z urn:sha1:3640cb54210edbb7edbf1b12ef0127ecfcea967d 'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image. Allow EVFILT_VNODE events to work on every filesystem type, not just 2005-06-09T20:20:31Z Suleiman Souhlal ssouhlal@FreeBSD.org 2005-06-09T20:20:31Z urn:sha1:679985d03a64f5dfb4355538ae6e3b70f8347f38 UFS by: - Making the pre and post hooks for the VOP functions work even when DEBUG_VFS_LOCKS is not defined. - Moving the KNOTE activations into the corresponding VOP hooks. - Creating a MNTK_NOKNOTE flag for the mnt_kern_flag field of struct mount that permits filesystems to disable the new behavior. - Creating a default VOP_KQFILTER function: vfs_kqfilter() My benchmarks have not revealed any performance degradation. Reviewed by: jeff, bde Approved by: rwatson, jmg (kqueue changes), grehan (mentor) - Mark the VOPs that require exclusive locks. Those that aren't marked 2005-04-11T15:19:29Z Jeff Roberson jeff@FreeBSD.org 2005-04-11T15:19:29Z urn:sha1:17c916e321300d28f52ad6b195cad88be48e8421 with E may be called with a shared lock held. This list really could be made per filesystem if we had any filesystems which differed from ffs in locking guarantees. VFS itself is not sensitive to this except where vgone() etc. are concerned. Sponsored by: Isilon Systems, Inc. - CLOSE, REVOKE, INACTIVE, and RECLAIM are not L L L, that's a locked vnode 2005-03-13T11:42:16Z Jeff Roberson jeff@FreeBSD.org 2005-03-13T11:42:16Z urn:sha1:4e6746965e14c0c0d60066ceaa0f056a8e4acf92 on enter, exit, error. This allows for the removal of the XLOCK. Sponsored by: Isilon Systems, Inc. VOP_DESTROYVOBJECT() is no more. 2005-02-07T09:26:58Z Poul-Henning Kamp phk@FreeBSD.org 2005-02-07T09:26:58Z urn:sha1:7ee4eb6192cf941878853e7f0dc60f51a39ca33a Take VOP_GETVOBJECT() out to pasture. We use the direct pointer now. 2005-01-25T00:42:16Z Poul-Henning Kamp phk@FreeBSD.org 2005-01-25T00:42:16Z urn:sha1:729fcf7efb348f5bce5ebfa3792eaf62e2d31dd5 Kill VOP_CREATEVOBJECT(), it is now the responsibility of the filesystem 2005-01-25T00:12:24Z Poul-Henning Kamp phk@FreeBSD.org 2005-01-25T00:12:24Z urn:sha1:69816ea35e4d1b72b19a41a8a76ccc501a4a8a22 for a given vnode to create a vnode_pager object if one is needed. Remove the unused credential argument from VOP_FSYNC() and VFS_SYNC(). 2005-01-11T07:36:22Z Poul-Henning Kamp phk@FreeBSD.org 2005-01-11T07:36:22Z urn:sha1:8df6bac4c74fad8167cbb05a2a358a36b1ce6f78 I'm not sure why a credential was added to these in the first place, it is not used anywhere and it doesn't make much sense: The credentials for syncing a file (ability to write to the file) should be checked at the system call level. Credentials for syncing one or more filesystems ("none") should be checked at the system call level as well. If the filesystem implementation needs a particular credential to carry out the syncing it would logically have to the cached mount credential, or a credential cached along with any delayed write data. Discussed with: rwatson /* -> /*- for copyright notices, minor format tweaks as necessary 2005-01-06T23:35:40Z Warner Losh imp@FreeBSD.org 2005-01-06T23:35:40Z urn:sha1:9454b2d864463f856c6aaf147851104b25cf4037 Make VOP_BMAP return a struct bufobj for the underlying storage device 2004-11-15T09:18:27Z Poul-Henning Kamp phk@FreeBSD.org 2004-11-15T09:18:27Z urn:sha1:9c83534dd8210476320b88e94c194d6b015d7192 instead of a vnode for it. The vnode_pager does not and should not have any interest in what the filesystem uses for backend. (vfs_cluster doesn't use the backing store argument.)