summaryrefslogtreecommitdiffstats
path: root/sys/miscfs/umapfs
Commit message (Collapse)AuthorAgeFilesLines
* Change #ifdef KERNEL to #ifdef _KERNEL in the public headers. "KERNEL"peter1999-12-291-2/+2
| | | | | | is an application space macro and the applications are supposed to be free to use it as they please (but cannot). This is consistant with the other BSD's who made this change quite some time ago. More commits to come.
* Second pass commit to introduce new ACL and Extended Attribute systemrwatson1999-12-191-0/+18
| | | | | | | calls, vnops, vfsops, both in /kern, and to individual file systems that require a vfsop_ array entry. Reviewed by: eivind
* Introduce NDFREE (and remove VOP_ABORTOP)eivind1999-12-151-0/+2
|
* Seperate the export check in VFS_FHTOVP, exports are now checked viaalfred1999-09-111-6/+17
| | | | | | | | | VFS_CHECKEXP. Add fh(open|stat|stafs) syscalls to allow userland to query filesystems based on (network) filehandle. Obtained from: NetBSD
* Fixed the previous change. Some more code controlled by UMAPFS_DIAGNOSTICbde1999-09-042-5/+3
| | | | is actually for diagnostics; control it with DIAGNOSTIC and not DDB.
* Converted the silly SAFTEY option into a new-style option by renaming it tobde1999-08-301-2/+2
| | | | | | DIAGNOSTIC. Fixed an English style bug in the panic messages controlled by SAFETY.
* Changed old-style options UMAPFS_DIAGNOSTIC and UMAP_DIAGNOSTIC to DEBUGbde1999-08-293-41/+43
| | | | | | or DDB and fixed printf format errors exposed by this. The options had little to do with diagnostics; they mostly controlled tracing of normal operation.
* $Id$ -> $FreeBSD$peter1999-08-284-4/+4
|
* Make sure that stat(2) and friends always return a valid st_dev field.phk1999-07-021-3/+1
| | | | | | Pseudo-FS need not fill in the va_fsid anymore, the syscall code will use the first half of the fsid, which now looks like a udev_t with major 255.
* Add a vnode argument to VOP_BWRITE to get rid of the last vnodemckusick1999-06-161-47/+1
| | | | | operator special case. Delete special case code from vnode_if.sh, vnode_if.src, umap_vnops.c, and null_vnops.c.
* Suser() simplification:phk1999-04-271-2/+2
| | | | | | | | | | | | | | | | | | | 1: s/suser/suser_xxx/ 2: Add new function: suser(struct proc *), prototyped in <sys/proc.h>. 3: s/suser_xxx(\([a-zA-Z0-9_]*\)->p_ucred, \&\1->p_acflag)/suser(\1)/ The remaining suser_xxx() calls will be scrutinized and dealt with later. There may be some unneeded #include <sys/cred.h>, but they are left as an exercise for Bruce. More changes to the suser() API will come along with the "jail" code.
* Don't allow anyone except root to mount file systems that map uids.imp1999-03-121-1/+7
| | | | | | | | | This can have bad security implications, but the impact on FreeBSD systems is minimal because this fs isn't in the default kernels and it is unknown if it even works. Submitted by: Manuel Bouyer <bouyer@antioche.eu.org> and Artur Grabowski <art@stacken.kth.se>
* Made this compile if UMAPFS_DIAGNOSTIC is defined. This has been brokenbde1999-01-011-2/+2
| | | | | since before rev.1.1, so UMAPFS_DIAGNOSTIC should not be trusted. UMAPFS_DIAGNOSTIC is commented out in LINT to hide various bugs.
* The "easy" fixes for compiling the kernel -Wunused: remove unreferenced staticarchie1998-12-071-3/+1
| | | | and local variables, goto labels, and functions declared but not defined.
* "fix" a warning that has been bugging me for ages. Eliminate a couplepeter1998-11-091-11/+10
| | | | | of temporary variables since they are only used once and their types were the cause of the warnings.
* Removed statically configured mount type numbers (MOUNT_*) and allbde1998-09-071-2/+2
| | | | | | | | | 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.
* Use [u]intptr_t instead of [u_]long for casts between pointers andbde1998-08-161-2/+3
| | | | integers. Don't forget to cast to (void *) as well.
* Fixed printf format errors.bde1998-07-301-21/+30
|
* VOP_STRATEGY grows an (struct vnode *) argumentjulian1998-07-041-2/+3
| | | | | | 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 <bde@freebsd.org>
* As described by the submitter:msmith1998-05-061-17/+1
| | | | | | | | | | | | | 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 <michaelh@cet.co.jp>
* The intent is to get rid of WILLRELE in vnode_if.src by makingmsmith1998-03-011-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <michaelh@cet.co.jp>
* Staticize.eivind1998-02-091-3/+3
|
* Fixed pagefault when cred == NOCRED.kato1998-02-072-14/+24
| | | | PR: 5632
* Fixed number of entries in gid-mapfile.kato1998-02-071-2/+2
| | | | PR: 5640
* Declare the variable `i' when UMAP_DIAGNOSTIC is defined.kato1998-02-031-1/+4
|
* Fixed missing initialization of mp->mnt_stat. At least vm depends onbde1998-01-011-1/+2
| | | | | | at least mp->mnt_stat.f_iosize being nonzero. PR: 5212
* Fix the same leak as in nullfs. Now the lowervp is properly marked inactive.roberto1997-10-211-1/+5
| | | | Reviewed by: phk
* Hmm, realign the vnops into two columns.phk1997-10-151-3/+3
|
* Stylistic overhaul of vnops tables.phk1997-10-151-14/+11
| | | | | | | 1. Remove comment stating the blatantly obvious. 2. Align in two columns. 3. Sort all but the default element alphabetically. 4. Remove XXX comments pointing out entries not needed.
* Last major round (Unless Bruce thinks of somthing :-) of malloc changes.phk1997-10-121-4/+6
| | | | | | | | Distribute all but the most fundamental malloc types. This time I also remembered the trick to making things static: Put "static" in front of them. A couple of finer points by: bde
* Executing binaries on a nullfs (or nullfs-based) filesystem results inphk1997-09-181-2/+3
| | | | | | | a trap. PR: 3104 Reviewed by: phk Submitted by: Dan Walters hannibal@cyberstation.net
* Some staticized variables were still declared to be extern.bde1997-09-071-2/+1
|
* Fix all areas of the system (or at least all those in LINT) to avoid storingwollman1997-08-161-3/+3
| | | | | | | | socket addresses in mbufs. (Socket buffers are the one exception.) A number of kernel APIs needed to get fixed in order to make this happen. Also, fix three protocol families which kept PCBs in mbufs to not malloc them instead. Delete some old compatibility cruft while we're at it, and add some new routines in the in_cksum family.
* Removed unused #includes.bde1997-08-023-10/+3
|
* Fix some warnings (missing prototypes, wrong "generic" args etc)peter1997-05-251-5/+6
| | | | umapfs uses one of nullfs's functions...
* Back out part 1 of the MCFH that changed $Id$ to $FreeBSD$. We are notpeter1997-02-224-4/+4
| | | | ready for it yet.
* Add missing function prototypes.mpp1997-02-123-3/+4
|
* This is the kernel Lite/2 commit. There are some requisite userlanddyson1997-02-104-58/+78
| | | | | | | | | | | | | | | changes, so don't expect to be able to run the kernel as-is (very well) without the appropriate Lite/2 userland changes. The system boots and can mount UFS filesystems. Untested: ext2fs, msdosfs, NFS Known problems: Incorrect Berkeley ID strings in some files. Mount_std mounts will not work until the getfsent library routine is changed. Reviewed by: various people Submitted by: Jeffery Hsu <hsu@freebsd.org>
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-144-4/+4
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Moved the fsnode MALLOC to before the call to getnewvnode() so that thedg1996-06-121-4/+14
| | | | | | | | process won't possibly block before filling in the fsnode pointer (v_data) which might be dereferenced during a sync since the vnode is put on the mnt_vnodelist by getnewvnode. Pointed out by Matt Day <mday@artisoft.com>
* Staticize.phk1995-12-112-42/+45
|
* Added prototypes.bde1995-12-033-6/+43
| | | | Removed some unnecessary #includes.
* null_node_find() and umap_node_find() were sometimes called without abde1995-12-031-2/+2
| | | | `struct mount *' arg. I don't know what the effects of this were.
* Introduced a type `vop_t' for vnode operation functions and usedbde1995-11-092-13/+13
| | | | | | | | | | | | | | | it 1138 times (:-() in casts and a few more times in declarations. This change is null for the i386. The type has to be `typedef int vop_t(void *)' and not `typedef int vop_t()' because `gcc -Wstrict-prototypes' warns about the latter. Since vnode op functions are called with args of different (struct pointer) types, neither of these function types is any use for type checking of the arg, so it would be preferable not to use the complete function type, especially since using the complete type requires adding 1138 casts to avoid compiler warnings and another 40+ casts to reverse the function pointer conversions before calling the functions.
* Remove trailing whitespace.rgrimes1995-05-304-36/+36
|
* Removed redundant newlines that were in some panic strings.dg1995-03-191-2/+2
|
* Add four more filesystem flags:wollman1995-03-161-2/+2
| | | | | | | | | | VFCF_NETWORK (this FS goes over the net) VFCF_READONLY (read-write mounts do not make any sense) VFCF_SYNTHETIC (data in this FS is not real) VFCF_LOOPBACK (this FS aliases something else) cd9660 is readonly; nullfs, umapfs, and union are loopback; NFS is netowkr; procfs, kernfs, and fdesc are synthetic.
* Add and move declarations to fix all of the warnings from `gcc -Wimplicit'bde1995-03-161-2/+1
| | | | | | (except in netccitt, netiso and netns) and most of the warnings from `gcc -Wnested-externs'. Fix all the bugs found. There were no serious ones.
* Cosmetics. reduce the noise from gcc -Wall.phk1994-10-103-22/+30
|
* More loadable VFS changes:wollman1994-09-221-1/+2
| | | | | | | | - Make a number of filesystems work again when they are statically compiled (blush) - FIFOs are no longer optional; ``options FIFO'' removed from distributed config files.
OpenPOWER on IntegriCloud