| Age | Commit message (Collapse) | Author |
|---|
|
an uvm aobj, copy out the signal trampoline into it and share that page
among all processes for the same emulation.
This also requires us to actually be able to tell signal code where the
trampoline is located, so introduce a new field in struct proc - p_sigcode
that is a pointer to sigcode. This allows us to remove all the ugly
calculations of the signal trampoline address done in every sendsig
function in the tree (that's why so many files are changed).
Tested by various people. ok deraadt@
|
|
|
|
|
|
|
|
|
|
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).
|
|
The flag can be either HOOK_REMOVE or HOOK_REMOVE|HOOK_FREE.
o HOOK_REMOVE removes the hook from the list before executing it.
o HOOK_FREE frees the hook after that.
- Let dostartuphooks use HOOK_REMOVE|HOOK_FREE so we can reclaim the memory.
- Let doshutdownhooks use HOOK_REMOVE so that when some shutdown hook
panics (they do that all the #@$%! time these days) we don't loop
for ever. Don't HOOK_FREE, it doesn't matter and I don't want to add
another possible panic condition for shutdown hooks.
- Actually free the pointer we're throwing away in hook_disestablish (I wonder
how much memory this has leaked over the years).
|
|
|
|
Implemented with paranoia.
|
|
|
|
|
|
declarations (extern int foo), and compensate in the appropriate locations.
|
|
ok art@ costa@
|
|
We'll never want to exec code in malloc mappings.
|
|
and i converted syslog to libevent and it works now (;
|
|
extent.
|
|
|
|
|
|
kjell@ says that it fixes his problems, noone else responded.
|
|
while pstat(8) expects a C structure abiding the regular structure packing
rules. This caused pstat -v to break on powerpc.
Unbreak the confusion by defining the structure in a common header file,
and having the kernel use it.
ok millert@ deraadt@
|
|
|
|
- modify getfeat to return something more useful to us on devices
(like lofn and everything else until jason fixes it) that can't
do rsa stuff, etc and can only do mod_exp..
- error handling fixes so we correctly fail to software when we can't
deal with a particular key size
- add sysctl kern.userasymcrypto to turn on/off userland asymmetric crypto
via /dev/crypto - 1 == on, 0 == off, default is off
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
info. Since we only use it to profile processes in user mode and there
is no way to get back user mode without going past the AST that will
write out the profiling info in a context where copyout works.
Sitting in my tree for ages.
Reviewed and with some suggestions from nordin@
|
|
infrastructure. ok art@ and miod@
|
|
have fun w/ pid_t cleanups.
millert@ ok
|
|
decriptor -> descriptor
authentciated -> authenticated
transmition -> transmission
|
|
initialization after domaininit().
|
|
|
|
|
|
that assume splbio, splassert(IPL_BIO) in it.
|
|
freed it.
Noticed by enami@netbsd in a recent discussion on tech-kern@netbsd.
Thanks to miod@ for helping me understand my code and realize that
what the discussion was originally about (a diff by itojun@) didn't apply
to us because I tweaked the semantics of closef() to solve the problem
automagically for us (and I forgot about it).
miod@ ok.
|
