Age | Commit message (Collapse) | Author |
|
'go for it' deraadt@
|
|
lock. Fixes a race as seen on PR kern/4915. Okay miod@ and joris@,
tested by krw@ and hshoexer@, thanks.
|
|
|
|
|
|
userland-visible sys/select.h. Consistent with what Net and Free do.
OK deraadt@, tested with full ports build by naddy@.
|
|
collisions with local variable names someone might make. this has bitten
me twice now and caused me to lose about 4 hours scratching my head when
nsensors just magically corrupts and gets bigger. at least my ram isnt
screwed.
ok marco@
|
|
been opened but the slave cannot be. We can't do the FILE_SET_MATURE
until we are past all possible error paths since it calls FRELE(),
resulting in a reference count of 0, which closef() panics on #ifdef
DIAGNOSTIC. OK deraadt@
|
|
|
|
of panics and bugfixes. Access curproc directly, do not expect a process
pointer as an argument. Should fix many "process context required" bugs.
Incentive and okay millert@, okay marc@. Various testing, thanks.
|
|
VOP_INACTIVE() in vrele() and vput(), we may sleep. Since there's no
locking of any kind, someone can vget() the vnode and vrele() it while
we sleep, beating us in getting the vnode on the free list.
|
|
|
|
purposes by the file system specific write routine. Fixes PR 4612.
Okay deraadt@.
|
|
|
|
mostly ok otto@ (ive since fixed the chunk he was worried about)
|
|
|
|
|
|
(some unusual linux binaries), ok deraadt.
|
|
the first element before iterating through the rest of them. stylistic
guidance from angela pascoe.
mark all tasks using the same argument as not running anymore, rather than
just the first one we bump into.
|
|
hairy at the moment, but its going into the tree so it can be worked on
and used.
|
|
tested on GENERIC and RAMDISK_CD to see if the small_kernel stuff stays
happy
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the protection of the memory mapping we're doing I/O on, or if we want to
leave them as they are. This should only be necessary for breakpoint
insertion in code, so we'll only use it for ptrace requests.
Initially from art@ after discussion with kettenis@ millert@ and I,
tested by many.
|
|
In fork1(), setup the p_{prof,virt}_to timeouts _before_ putting the process
on the runqueue. Since SCHED_UNLOCK() can cause pre-emption, it is possible
(with the old code) for the newly created process to run and become curproc
before the timeouts were set. If itimers are set early, and you're unlucky,
hardclock() might fire at this time and attempt timeout_add() on the unset
timeouts, leading to "panic: timeout_add: not initialized".
deraadt@, miod@ ok
|
|
from alexander bluhm; ok deraadt
|
|
from ray lai;
|
|
|
|
the midst of exiting. This solves a race condition that causes freed memory
to be left referenced in the master kernel timeout worklist, leading to a
uvm_fault. The same race condition was already fixed earlier in r1.53 of
kern_clock.c for the process virtual and profile timeout structs.
deraadt@ ok, testing by krw@
|
|
wrong direction for large offsets as nick@ saw. With tom@ and toby@;
ok tdeval@ krw@
|
|
in the buffer lists by removing a buffer from the hash twice. Problem
identified in discussion with Alexander Bluhm <Alexander_Bluhm@genua.de>.
|
|
reclaimed while in this sensitive time frame. That is needed when we
don't have locks. Should fix the 'sched_sync: fsync failed' panic some
people were seeing.
Testing mostly by sturm@ and krw@, okay tedu@ and deraadt@.
|
|
is in the midst of exiting. This solves a race condition that causes freed
memory to be left referenced in the master kernel timeout worklist, leading to
a uvm_fault (observed on an i386 MP system). tedu@, deraadt@, miod@ ok
|
|
|
|
instead of the contents of a for() loop. No functional change.
From the m88k SMP tree; ok art@ deraadt@
[complete diff this time]
|
|
|
|
instead of the contents of a for() loop. No functional change.
From the m88k SMP tree; ok art@ deraadt@
|
|
|
|
ok miod@
|
|
arches; except on sparc where the range is 4-8 for !sun4m and 4-64 for sun4m,
selected at runtime.
|
|
to CTL_MAXNAME; ok espie uwe
|
|
|
|
|
|
to FREAD/FWRITE. OK deraadt@
|
|
|
|
- Don't copy the pathbuf into kernel space unless we're systracing.
deraadt@ ok
|
|
size of an fd_set (ie. 256 bits), to avoid the malloc. that is a lot
of local storage. change the cross-over point to 32-bits, which is more
fair. if you select with large widths, you pay the price. tested by
dlg, read by millert and pascoe, run on all machines
|