summaryrefslogtreecommitdiffstats
path: root/sys/fs
Commit message (Collapse)AuthorAgeFilesLines
* Convert select -> poll.peter1997-09-1410-106/+127
| | | | | Delete 'always succeed' select/poll handlers, replaced with generic call. Flag missing vnode op table entries.
* Fix a type in a comment and remove some checks now done centrally.phk1997-09-101-10/+2
|
* This stuff is now done centrally.phk1997-09-101-15/+1
|
* Removed yet more vestiges of config-time swap configuration and/orbde1997-09-071-8/+3
| | | | cleaned up nearby cruft.
* Staticized.bde1997-09-071-3/+3
|
* Some staticized variables were still declared to be extern.bde1997-09-076-13/+8
|
* Support read-only mount.kato1997-09-041-1/+39
|
* Removed unused #includes.bde1997-09-028-32/+8
|
* Include "opt_ddb.h" only when NULLFS_DIAGNOSTIC is defined.kato1997-08-281-3/+3
|
* Fixed NULLFS_DIAGNOSTIC stuff.kato1997-08-271-2/+11
|
* Uncut&paste cache_lookup().phk1997-08-266-119/+14
| | | | | | | | | | | | | | | This unifies several times in theory indentical 50 lines of code. The filesystems have a new method: vop_cachedlookup, which is the meat of the lookup, and use vfs_cache_lookup() for their vop_lookup method. vfs_cache_lookup() will check the namecache and pass on to the vop_cachedlookup method in case of a miss. It's still the task of the individual filesystems to populate the namecache with cache_enter(). Filesystems that do not use the namecache will just provide the vop_lookup method as usual.
* Back out some incorrect changes that was worse than the original bug.dyson1997-08-261-3/+1
|
* Added a sysctl arg, vfs.cd9660.doclusterread. Deleted debug andkato1997-08-251-16/+18
| | | | !FreeBSD code arround cluster read stuff.
* This is a trial improvement for the vnode reference count while on the vnodedyson1997-08-221-2/+4
| | | | | | free list problem. Also, the vnode age flag is no longer used by the vnode pager. (It is actually incorrect to use then.) Constructive feedback welcome -- just be kind.
* Fix all areas of the system (or at least all those in LINT) to avoid storingwollman1997-08-1610-31/+32
| | | | | | | | 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.
* Added DIAGNOSTIC routine to test inconsistency of vnode when cnpkato1997-08-151-1/+9
| | | | | | points `.'. Obtained from: NetBSD
* Deleted unused code which adjust UN_UNLOCK flag.kato1997-08-151-17/+5
|
* If the user doesn't have read permission, union_copyup should not copykato1997-08-141-1/+11
| | | | | | a file to upper layer. Reviewed by: Naofumi Honda <honda@Kururu.math.sci.hokudai.ac.jp>
* Backed out part of previous change. The example of -b mount inkato1997-08-141-4/+2
| | | | manpage works again.
* Fixed vnode corruption by undefined case in union_lookup(). Whenkato1997-08-121-3/+7
| | | | | | | | | | | uerror == 0 && lerror == EACCES, lowervp == NULLVP and union_allocvp doesn't find existing union node and new union node is created. Sicne it is dificult to cover all the case, union_lookup always returns when union_lookup1() returns EACCES. Submitted by: Naofumi Honda <honda@Kururu.math.sci.hokudai.ac.jp> Obtained from: NetBSD/pc98
* Check permissions for fp regs as well as normal regs.sef1997-08-121-1/+3
|
* Fix procfs security hole -- check permissions on meaningful I/Os (namely,sef1997-08-124-8/+43
| | | | | | | reading/writing of mem and regs). Also have to check for the requesting process being group KMEM -- this is a bit of a hack, but ps et al need it. Reviewed by: davidg
* Removed unused #includes.bde1997-08-0227-124/+28
|
* More comment cleanup.alex1997-06-261-5/+5
|
* Typo police.alex1997-06-261-3/+3
|
* Style fix my previous commit.alex1997-06-261-2/+2
|
* Block all write operations to /proc/1/* when securelevel > 0.alex1997-06-211-1/+3
| | | | | | | The additional check in procfs_ctl.c could be backed out, but I'm leaving it in for good measure. Reviewed by: Theo de Raadt <deraadt@OpenBSD.org>
* Don't remove the controlling tty from the session if the vnode is beingtegge1997-05-291-1/+2
| | | | cleaned. This should help for PR kern/3581.
* Fix some warnings (missing prototypes, wrong "generic" args etc)peter1997-05-253-9/+11
| | | | umapfs uses one of nullfs's functions...
* Remove redundant check for vp == dvp (done in VFS before calling).phk1997-05-171-10/+1
|
* 1. Added cast and parenthesis in block size calculaion inkato1997-05-072-78/+78
| | | | | | | union_statfs(). 2. staticized union vops. Submitted by: Doug Rabson <dfr@nlsystems.com>
* Hide the kernel-only stuff inside #ifdef KERNEL.joerg1997-05-071-5/+14
| | | | | | XXX should be #ifdef _KERNEL XXX^2 the !KERNEL part should probably be moved out into a publically visible header file anyway.
* Oops. The function cd9660_mountroot() is gone, but i've committed anjoerg1997-05-041-3/+1
| | | | even more bogus prototype for it in my previous commit.
* This mega-commit brings the following:joerg1997-05-042-19/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | . It makes cd9660 root f/s working again. . It makes CD9660 a new-style option. . It adds support to mount an ISO9660 multi-session CD-ROM as the root filesystem (the last session actually, but that's what is expected behaviour). Sigh. The CDIOREADTOCENTRYS did a copyout() of its own, and thus has been unusable for me for this work. Too bad it didn't simply stuff the max 100 entries into the struct ioc_read_toc_entry, but relied on a user supplied data buffer instead. :-( I now had to reinvent the wheel, and created a CDIOREADTOCENTRY ioctl command that can be used in a kernel context. While doing this, i noticed the following bogosities in existing CD-ROM drivers: wcd: This driver is likely to be totally bogus when someone tries two succeeding CDIOREADTOCENTRYS (or now CDIOREADTOCENTRY) commands with requesting MSF format, since it apparently operates on an internal table. scd: This driver apparently returns just a single TOC entry only for the CDIOREADTOCENTRYS command. I have only been able to test the CDIOREADTOCENTRY command with the cd(4) driver. I hereby request the respective maintainers of the other CD-ROM drivers to verify my code for their driver. When it comes to merging this CD-ROM multisession stuff into RELENG_2_2 i will only consider drivers where i've got a confirmation that it actually works.
* Fixed panic message in union_lock(): union_link --> union_lock.kato1997-05-031-2/+2
|
* Access correct union mount point in union_access. Old vnode is savedkato1997-05-021-2/+4
| | | | | | in savedvp variable and it is used for the argument of MOUNTTOUNIONMOUNT(). I didn't realize ap->a_vp is modified before MOUNTTOUNIONMOUNT(), so the change by revision 1.22 is incorrect.
* Remove the dependancy on DEV_BSIZE, now specfs works on != 512bytesos1997-05-011-3/+10
| | | | | sector devices given that the fs uses a blocksize of at least a physical sector size.
* For multi-session CD-ROMs, we have to account for previous sessions asjoerg1997-04-291-1/+10
| | | | well in volume_space_size. Otherwise, NFS exports won't work.
* Add support for ISO9660 multi-session CD-ROMs. This is just nothingjoerg1997-04-292-2/+5
| | | | | | | | | | but searching the directory on something else than the default location. NB: this comprises an interface change to the mount_cd9660(8) utility (commit will follow). You need to rebuild both. I've got similar patches for RELENG_2_2, should i commit them too?
* Revised fix for locking violation when unionfs calls vput withkato1997-04-291-32/+36
| | | | | | | | | | | | | | | | | UN_KLOCK flag. When UN_KLOCK is set, VOP_UNLOCK should keep uppervp locked and clear UN_ULOCK flag. To do this, when UN_KLOCK is set, (1) union_unlock clears UN_ULOCK and does not clear UN_KLOCK, (2) union_lock() does not access uppervp and does not clear UN_KLOCK, and (3) callers of vput/VOP_UNLOCK should clear UN_KLOCK. For example, vput becomes: SETKLOCK(union_node); vput(vnode); CLEARKLOCK(union_node); where SETKLOCK macro sets UN_KLOCK and CLEARKLOCK macro clears UN_KLOCK.
* Removed bogon from previous commit: doubly included sys/systm.h.alex1997-04-271-2/+1
|
* Prevent debugger attachment to init when securelevel > 0.alex1997-04-271-1/+6
| | | | Noticed by: Brian Buchanan <brian@wasteland.calbbs.com>
* Undo 1.29.kato1997-04-271-2/+2
|
* Do nothing instead of adjusting un_flags when (uppervp is locked) &&kato1997-04-261-11/+3
| | | | | (UN_ULOCK is not set) in union_lock. This condition may indicate race. DIAGNOSTIC kernel still panic here.
* Do not clear UN_ULOCK in certain case.kato1997-04-261-2/+12
| | | | | | | | | Our vput calls vm_object_deallocate() --> vm_object_terminate(). The vm_object_terminate() calls vn_lock(), since UN_LOCKED has been already cleared in union_unlock(). Then, union_lock locks upper vnode when UN_ULOCK is not set. The upper vnode is not unlocked when UN_KLOCK is set in union_unlock(), thus, union_lock tries to lock locked vnode and we get panic.
* Dirty change in union_lock(). Sometimes upper vnode is locked withoutkato1997-04-211-5/+23
| | | | | | | | UN_ULOCK flag. This shows a locking violation but I couldn't find the reason UN_ULOCK is not set or upper vnode is not unlocked. I added the code that detect this case and adjust un_flags. DIAGNOSTIC kernel doesn't adjust un_flags, but just panic here to help debug by kernel hackers.
* Replace VOP_LOCK with vn_lock.kato1997-04-211-2/+2
|
* Fix both a problem with accessing backing objects, and also releasedyson1997-04-201-1/+14
| | | | | | the process map on nonexistant pages. PR: kern/3327 Submitted by: Tor Egge <Tor.Egge@idi.ntnu.no>
* Avoid `lock against myself' panic by following operation:kato1997-04-192-6/+33
| | | | | | | | | | # mount -t union (or null) dir1 dir2 # mount -t union (or null) dir2 dir1 The function namei in union_mount calls union_root. The upper vnode has been already locked and vn_lock in union_root causes above panic. Add printf's included in `#ifdef DIAGNOSTIC' for EDEADLK cases.
* Fix `locking against myself' panic by multi nullfs mount of samekato1997-04-171-1/+25
| | | | directory pair.
OpenPOWER on IntegriCloud