| Age | Commit message (Collapse) | Author |
|---|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
ufs1_daddr_t, a few to daddr_t. ufs_daddr_t typedef is retained, but consider
it deprecated. no functional changes. inspired by freebsd. ok art@
|
|
|
|
force the unmount, so there's no need to mess with resetting
processes' working dirs.
|
|
won't always work, but it's the best we can do for now. this covers
at least some of the failure cases the previous commit to vfs_lookup.c
checks for.
ok weingart@
|
|
help testing and eyeballing henric tdeval miod
ok costa deraadt
|
|
|
|
|
|
- cache_lookup
move common code from various fs's here
always return with vnode and parent locked
adjust return codes
- PDIRUNLOCK - new flag set if lookup couldn't lock parent vnode
- kernfs and procfs
lock vnode in get_root
don't unlock (again) in kernfs_freevp
fix memory leak in procfs
From tedu@stanford.edu
deraadt@ and various other ok
|
|
Reported by Dave Steinberg <lists@redterror.net>
|
|
The inheritace is implemented by setting the default vnodeop to a
bypass op that repeats the operation on the spec/fifo vnodeop vector.
The overhead of one extra indirect function call is worth the cleanup
and improved correctness.
This actually solves a few bugs where some vnode ops were missing from
some vectors (like kqfilter or revoke). (and even more on the ubc
branch).
Inspired by the same thing done in FreeBSD.
|
|
|
|
Diff generated by Chris Kuethe.
|
|
|
|
|
|
ibcs2_stat.c one OK by provos@
|
|
files up to 16TB, we do limit the max file to 2^31 pages to prevent
overflow of a 32-bit unsigned int. The buffer cache has its own
checks but a little added paranoia never hurts. Adapted from a patch
in FreeBSD.
|
|
ext2fs, inode numbers start at 1, so the maximum valid inode number
is (s_inodes_per_group * s_groups_count), not one less.
From FreeBSD.
costa@ ok.
|
|
|
|
|
|
Fix two problems with softdep_typenames (missing entry, wrong boundary check);
wiz@netbsd.org
art@ OK
|
|
to get shared locks for lookup and get the exclusive lock only with
LK_DRAIN on unmount and do the real exclusive locking with flags in
mnt_flags, we now use shared locks for lookup and an exclusive lock for
unmount.
This is accomplished by slightly changing the semantics of vfs_busy.
Old vfs_busy behavior:
- with LK_NOWAIT set in flags, a shared lock was obtained if the
mountpoint wasn't being unmounted, otherwise we just returned an error.
- with no flags, a shared lock was obtained if the mountpoint was being
unmounted, otherwise we slept until the unmount was done and returned
an error.
LK_NOWAIT was used for sync(2) and some statistics code where it isn't really
critical that we get the correct results.
0 was used in fchdir and lookup where it's critical that we get the right
directory vnode for the filesystem root.
After this change vfs_busy keeps the same behavior for no flags and LK_NOWAIT.
But if some other flags are passed into it, they are passed directly
into lockmgr (actually LK_SLEEPFAIL is always added to those flags because
if we sleep for the lock, that means someone was holding the exclusive lock
and the exclusive lock is only held when the filesystem is being unmounted.
More changes:
dounmount must now be called with the exclusive lock held. (before this
the caller was supposed to hold the vfs_busy lock, but that wasn't always
true).
Zap some (now) unused mount flags.
And the highlight of this change:
Add some vfs_busy calls to match some vfs_unbusy calls, especially in
sys_mount. (lockmgr doesn't detect the case where we release a lock noone
holds (it will do that soon)).
If you've seen hangs on reboot with mfs this should solve it (I repeat this
for the fourth time now, but this time I spent two months fixing and
redesigning this and reading the code so this time I must have gotten
this right).
|
|
|
|
|
|
was introduced, but now it causes crashes when kernels are built
without DIAGNOSTIC. Instead of trying to debug this incorrect code,
I'm just removing this abomination.
|
|
|
|
|
|
|
|
I'm not completly sure it's needed, but better safe than sorry. And this
simplifies some spl assertions in the still not comitted splassert code.
|
|
ok millert@, art@
|
|
Synch files that use that field.
(This argument is an internal interface specific to OpenBSD, so it won't
cause compatibility problems.)
(No bump, not an ABI change).
ok art, millert...
|
|
with UFS_EXTATTR_AUTOSTART. thanks dlucq. ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fix from NetBSD
pr#1693
art@ OK
|
|
|
|
|
|
|
|
We no longer use the last arg to WORKITEM_FREE but I have not removed it
from the calls in order to simplify these diffs and further softdep merges.
|
|
|
|
well (not at all) with shortages of the vm_map where the pages are mapped
(usually kmem_map).
Try to deal with it:
- group all information the backend allocator for a pool in a separate
struct. The pool will only have a pointer to that struct.
- change the pool_init API to reflect that.
- link all pools allocating from the same allocator on a linked list.
- Since an allocator is responsible to wait for physical memory it will
only fail (waitok) when it runs out of its backing vm_map, carefully
drain pools using the same allocator so that va space is freed.
(see comments in code for caveats and details).
- change pool_reclaim to return if it actually succeeded to free some
memory, use that information to make draining easier and more efficient.
- get rid of PR_URGENT, noone uses it.
|
|
|
|
update the modification time -- required by POSIX. ok millert@ drahn@
|
|
From FreeBSD
|
|
machines or some configurations or in some phase of the moon (we actually
don't know when or why) files disappeared. Since we've not been able to
track down the problem in two weeks intense debugging and we need -current
to be stable, back out everything to a state it had before UBC.
We apologise for the inconvenience.
|
