summaryrefslogtreecommitdiffstats
path: root/sys/kern/vfs_default.c
Commit message (Collapse)AuthorAgeFilesLines
...
* Add marker vnodes to ensure that all vnodes associated with the mount point aretegge2006-01-091-3/+5
| | | | | | iterated over when using MNT_VNODE_FOREACH. Reviewed by: truckman
* Eradicate caddr_t from the VFS API.des2005-12-141-1/+1
|
* In vop_stdpathconf(ap) also default for _PC_NAME_MAX and _PC_PATH_MAX.phk2005-08-171-0/+6
|
* - Replace the series of DEBUG_LOCKS hacks which tried to save the vn_lockjeff2005-08-031-5/+0
| | | | | | | caller by saving the stack of the last locker/unlocker in lockmgr. We also put the stack in KTR at the moment. Contributed by: Antoine Brodin <antoine.brodin@laposte.net>
* - Add and enhance asserts related to the wrong bufobj panic.jeff2005-06-141-0/+3
| | | | | Sponsored by: Isilon Systems, Inc. Approved by: re (blanket vfs)
* Allow EVFILT_VNODE events to work on every filesystem type, not justssouhlal2005-06-091-0/+8
| | | | | | | | | | | | | | | 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)
* - Remove unnecessary spls.jeff2005-05-011-10/+2
|
* - Now that writes to character devices supporting softupdates canjeff2005-04-031-3/+4
| | | | | | | | | generate dirty bufs even with a locked vnode, 100 retries is not that many. This should probably change from a retry count to an abort when we are no longer cleaning any buffers. - Don't call vprint() while we still hold the vnode locked. Move the call to later in the function. - Clean up a comment.
* - Fixup the default vfs_root function to match the new prototype.jeff2005-03-241-1/+2
| | | | Sponsored by: Isilon Systems, Inc.
* - Don't drop the lock in the default inactive handler anymore, VOP_NULLjeff2005-03-131-14/+1
| | | | | | will do for vop_stdinactive now. Sponsored by: Isilon Systems, Inc.
* Remove VFS_START(). Its original purpose involved the mfs filesystem,das2005-02-201-10/+0
| | | | | | | which is long gone. Discussed with: mckusick Reviewed by: phk
* Remove vop_stddestroyvobject()phk2005-02-071-13/+0
|
* Move the contents of vop_stddestroyvobject() to the new vnode_pagerphk2005-01-281-26/+2
| | | | | | | function vnode_destroy_vobject(). Make the new function zero the vp->v_object pointer so we can tell if a call is missing.
* Take VOP_GETVOBJECT() out to pasture. We use the direct pointer now.phk2005-01-251-24/+0
|
* Kill VOP_CREATEVOBJECT(), it is now the responsibility of the filesystemphk2005-01-251-14/+0
| | | | for a given vnode to create a vnode_pager object if one is needed.
* Move the body of vop_stdcreatevobject() over to the vnode_pager underphk2005-01-241-50/+1
| | | | | | | | | | | the name Sande^H^H^H^H^Hvnode_create_vobject(). Make the new function take a size argument which removes the need for a VOP_STAT() or a very pessimistic guess for disks. Call that new function from vop_stdcreatevobject(). Make vnode_pager_alloc() private now that its only user came home.
* Kill the VV_OBJBUF and test the v_object for NULL instead.phk2005-01-241-2/+1
|
* - Remove GIANT_REQUIRED where it is no longer required.jeff2005-01-241-4/+0
| | | | Sponsored By: Isilon Systems, Inc.
* Ditch vfs_object_create() and make the callers call VOP_CREATEVOBJECT()phk2005-01-131-1/+1
| | | | directly.
* Remove the unused credential argument from VOP_FSYNC() and VFS_SYNC().phk2005-01-111-5/+3
| | | | | | | | | | | | | | | | | | 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 necessaryimp2005-01-061-1/+1
|
* Add missing vop_bypass (returning EOPNOTSUPP).phk2004-12-031-1/+3
| | | | Tripped up: marks
* Back when VOP_* was introduced, we did not have new-style structphk2004-12-011-42/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | initializations but we did have lofty goals and big ideals. Adjust to more contemporary circumstances and gain type checking. Replace the entire vop_t frobbing thing with properly typed structures. The only casualty is that we can not add a new VOP_ method with a loadable module. History has not given us reason to belive this would ever be feasible in the the first place. Eliminate in toto VOCALL(), vop_t, VNODEOP_SET() etc. Give coda correct prototypes and function definitions for all vop_()s. Generate a bit more data from the vnode_if.src file: a struct vop_vector and protype typedefs for all vop methods. Add a new vop_bypass() and make vop_default be a pointer to another struct vop_vector. Remove a lot of vfs_init since vop_vector is ready to use from the compiler. Cast various vop_mumble() to void * with uppercase name, for instance VOP_PANIC, VOP_NULL etc. Implement VCALL() by making vdesc_offset the offsetof() the relevant function pointer in vop_vector. This is disgusting but since the code is generated by a script comparatively safe. The alternative for nullfs etc. would be much worse. Fix up all vnode method vectors to remove casts so they become typesafe. (The bulk of this is generated by scripts)
* Make more sense out of vop_stdcreatevobject()phk2004-11-181-21/+21
|
* Make VOP_BMAP return a struct bufobj for the underlying storage devicephk2004-11-151-3/+3
| | | | | | | | | 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.)
* The default VOP_REVOKE() should be vop_panic() as we should neverphk2004-11-131-1/+1
| | | | get here in the first place.
* Properly implement a default version of VOP_GETWRITEMOUNT.phk2004-11-061-0/+1
| | | | | Remove improper access to vop_stdgetwritemount() which should and will instead rely on the VOP default path.
* Move a call to wakeup() from vm_object_terminate() to vnode_pager_dealloc()alc2004-11-061-0/+1
| | | | | | | | | because this call is only needed to wake threads that slept when they discovered a dead object connected to a vnode. To eliminate unnecessary calls to wakeup() by vnode_pager_dealloc(), introduce a new flag, OBJ_DISCONNECTWNT. Reviewed by: tegge@
* Remove VOP_SPECSTRATEGY() from the system.phk2004-10-291-1/+0
|
* Eliminate unnecessary KASSERT.phk2004-10-271-3/+0
| | | | | Eliminate a printf which would never tell us anything anyway because the KASSERT would have triggered.
* Loose the v_dirty* and v_clean* alias macros.phk2004-10-251-4/+3
| | | | | Check the count field where we just want to know the full/empty state, rather than using TAILQ_EMPTY() or TAILQ_FIRST().
* Move the VI_BWAIT flag into no bo_flag element of bufobj and call it BO_WWAITphk2004-10-211-9/+7
| | | | | | | | | | Add bufobj_wref(), bufobj_wdrop() and bufobj_wwait() to handle the write count on a bufobj. Bufobj_wdrop() replaces vwakeup(). Use these functions all relevant places except in ffs_softdep.c where the use if interlocked_sleep() makes this impossible. Rename b_vnbufs to b_bobufs now that we touch all the relevant files anyway.
* Use vn_isdisk() to check if vnode is a disk.phk2004-09-241-1/+1
| | | | (repeat, CVS core dumped on me)
* use vn_isdisk() to see if vnode is a disk.phk2004-09-241-1/+1
|
* Make VFS_ROOT() and vflush() take a thread argument.alfred2004-07-121-1/+2
| | | | | | This is to allow filesystems to decide based on the passed thread which vnode to return. Several filesystems used curthread, they now use the passed thread.
* style(9)alfred2004-07-071-1/+12
|
* do the vfsstd thing instead of messing up our VFS_SYSCTL macro.alfred2004-07-071-0/+10
|
* When we traverse the vnodes on a mountpoint we need to look out forphk2004-07-041-9/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | our cached 'next vnode' being removed from this mountpoint. If we find that it was recycled, we restart our traversal from the start of the list. Code to do that is in all local disk filesystems (and a few other places) and looks roughly like this: MNT_ILOCK(mp); loop: for (vp = TAILQ_FIRST(&mp...); (vp = nvp) != NULL; nvp = TAILQ_NEXT(vp,...)) { if (vp->v_mount != mp) goto loop; MNT_IUNLOCK(mp); ... MNT_ILOCK(mp); } MNT_IUNLOCK(mp); The code which takes vnodes off a mountpoint looks like this: MNT_ILOCK(vp->v_mount); ... TAILQ_REMOVE(&vp->v_mount->mnt_nvnodelist, vp, v_nmntvnodes); ... MNT_IUNLOCK(vp->v_mount); ... vp->v_mount = something; (Take a moment and try to spot the locking error before you read on.) On a SMP system, one CPU could have removed nvp from our mountlist but not yet gotten to assign a new value to vp->v_mount while another CPU simultaneously get to the top of the traversal loop where it finds that (vp->v_mount != mp) is not true despite the fact that the vnode has indeed been removed from our mountpoint. Fix: Introduce the macro MNT_VNODE_FOREACH() to traverse the list of vnodes on a mountpoint while taking into account that vnodes may be removed from the list as we go. This saves approx 65 lines of duplicated code. Split the insmntque() which potentially moves a vnode from one mount point to another into delmntque() and insmntque() which does just what the names say. Fix delmntque() to set vp->v_mount to NULL while holding the mountpoint lock.
* Remove advertising clause from University of California Regent's license,imp2004-04-051-4/+0
| | | | | | per letter dated July 22, 1999. Approved by: core
* Clean up the stub fake vnode locking implemenations. The main reason thispeter2004-03-291-160/+0
| | | | | | | | | | | | stuff was here (NFS) was fixed by Alfred in November. The only remaining consumer of the stub functions was umapfs, which is horribly horribly broken. It has missed out on about the last 5 years worth of maintenence that was done on nullfs (from which umapfs is derived). It needs major work to bring it up to date with the vnode locking protocol. umapfs really needs to find a caretaker to bring it into the 21st century. Functions GC'ed: vop_noislocked, vop_nolock, vop_nounlock, vop_sharedlock.
* Remove mntvnode_mtx and replace it with per-mountpoint mutex.kan2003-11-051-5/+5
| | | | | | | | | | Introduce two new macros MNT_ILOCK(mp)/MNT_IUNLOCK(mp) to operate on this mutex transparently. Eventually new mutex will be protecting more fields in struct mount, not only vnode list. Discussed with: jeff
* Take care not to call vput if thread used in corresponding vgetkan2003-11-021-1/+2
| | | | | | | | | | wasn't curthread, i.e. when we receive a thread pointer to use as a function argument. Use VOP_UNLOCK/vrele in these cases. The only case there td != curthread known at the moment is boot() calling sync with thread0 pointer. This fixes the panic on shutdown people have reported.
* Temporarily undo parts of the stuct mount locking commit by jeff.kan2003-11-011-5/+1
| | | | | | | | It is unsafe to hold a mutex across vput/vrele calls. This will be redone when a better locking strategy is agreed upon. Discussed with: jeff
* Relock mntvnode_mtx if vget fails in vfs_stdsync. The loop iskan2003-10-301-0/+1
| | | | always shoould entered with mutex locked.
* Introduce no_poll() default method for device drivers. Have itphk2003-09-271-0/+1
| | | | | | | | | | | | | | | | | | | | do exactly the same as vop_nopoll() for consistency and put a comment in the two pointing at each other. Retire seltrue() in favour of no_poll(). Create private default functions in kern_conf.c instead of public ones. Change default strategy to return the bio with ENODEV instead of doing nothing which would lead the bio stranded. Retire public nullopen() and nullclose() as well as the entire band of public no{read,write,ioctl,mmap,kqfilter,strategy,poll,dump} funtions, they are the default actions now. Move the final two trivial functions from subr_xxx.c to kern_conf.c and retire the now empty subr_xxx.c
* I have not had any reports of trouble for a long time, so remove thephk2003-06-151-25/+3
| | | | | gentle versions of the vop_strategy()/vop_specstrategy() mismatch methods and use vop_panic() instead.
* Use __FBSDID().obrien2003-06-111-3/+3
|
* Lock the vm_object when performing vm_pager_deallocate().alc2003-05-061-1/+1
|
* Lock access to the vm_object's flags in vop_stdcreatevobject().alc2003-05-021-1/+4
|
* Lock an update to a vm_object's ref_count.alc2003-05-011-0/+2
|
OpenPOWER on IntegriCloud