| Age | Commit message (Collapse) | Author |
|---|
|
|
|
pfsyncstart() does not require the big lock, make it use the ifq API.
OK mvs
|
|
Hints from kettenis@, ok kettenis@ deraadt@
|
|
Rearrange the critical section in setitimer(2) to match that of
getitimer(2). This will make it easier to merge the two critical
sections in a subsequent diff.
In particular, we want to write the new timer value in *one* place in
the code, regardless of which timer we're setting.
ok millert@
|
|
in the received message.
ok patrick@
|
|
When record protection is engaged, the plaintext must be followed by a
non-zero content type and optional zero padding. If the plaintext is zero
length or only consists of zero bytes then it is not a valid message,
since the content type is unspecified.
ok tb@
|
|
ok inoguchi@ tb@
|
|
ok inoguchi@ tb@
|
|
ok inoguchi@ tb@
|
|
The error path does the same as the currently duplicated code.
ok inoguchi@ tb@
|
|
For what are probably historical reasons, setitimer(2) does not
validate its input (itv) immediately after copyin(9). Instead, it
waits until after (possibly) performing a getitimer(2) to copy out the
state of the timer.
Consolidating copyin(9), input validation, and input conversion into a
single block before the getitimer(2) operation makes setitimer(2)
itself easier to read. It will also simplify merging the critical
sections of setitimer(2) and getitimer(2) in a subsequent patch.
This changes setitimer(2)'s behavior in the EINVAL case. Currently,
if your input (itv) is invalid, we return EINVAL *after* modifying the
output (olditv). With the patch we will now return EINVAL *before*
modifying the output. However, any code dependent upon this behavior
is broken: the contents of olditv are undefined in all setitimer(2)
error cases.
ok millert@
|
|
|
|
The ITIMER_REAL per-process interval timer is protected by the kernel
lock. The ITIMER_REAL timeout (ps_realit_to), setitimer(2), and
getitimer(2) all run under the kernel lock. Entering itimer_mtx
during getitimer(2) when reading the ITIMER_REAL ps_timer state is
superfluous and misleading.
|
|
it.
Prepares for removal of #include <scsi/scsi_debug.h> from scsiconf.h as soon as
the alpha tester digs out from hurricane to compile last untested files.
|
|
The ITIMER_REAL itimerspec (ps_timer[0]) and timeout (ps_realit_to)
are protected by the kernel lock. Annotate them with "K".
The ITIMER_VIRTUAL and ITIMER_PROF itimerspecs (ps_timer[1],
ps_timer[2]) are protected by itimer_mtx. Annotate them with "T",
for "timer".
With input from kettenis@ and anton@.
ok kettenis@, anton@
|
|
|
|
keys in addition to its current flag options. Time-limited keys will
automatically be removed from ssh-agent after their expiry time has
passed; ok markus@
|
|
respect $SSH_ASKPASS_REQUIRE; ok markus@
|
|
of fixes and a few new APIs that we'd like to use in OpenSSH
ok deraadt@
|
|
was right that this isn't really needed. Now the list is the same as what
we had for the previous compiler-rt version.
|
|
Restore them to their previous values.
|
|
|
|
|
|
From sxvghd (at) firemail (dot) cc, on tech@
|
|
|
|
ok kettenis@
|
|
ok kettenis@
|
|
ok kettenis@
|
|
ok kettenis@
|
|
|
|
ok patrick@
|
|
If a peer sends a bogus record consisting of all-zero plaintext,
the content_len would be decremented to -1 and cause a crash in
freezero.
ok inoguchi jsing
|
|
system would deadlock when a CPU gets blocked by the mutex while another
CPU is waiting for the first CPU to finish a rendezvous request.
This possibly fixes some hangs on sgi. There should be no effect on
loongson and octeon because their interrupt code is sloppy with masking
of IPIs.
While here, rename the rendezvous mutex to better reflect its use.
|
|
This is the lib/builtin directory of the compiler-rt source tarball.
comments/ok patrick@, ok kettenis@
|
|
|
|
nestled together. Rename scsibusprint() to scsibussubprint() since it is used
with scsibussubmatch().
|
|
simplifications, add missing markup, and break an overlong line
|
|
packets output out of KERNEL_LOCK. pppac(4) and pipex(4) are ready to
this.
ok yasuoka@
|
|
main needs to understand the kstat_tree type now, so move the
declaration up.
|
|
|
|
ok kn@
|
|
This is the documented behaviour which was changed by pedro in rev 1.81
which was partially backed out in rev 1.82.
|
|
reverts changes from msdosfs_vfsops.c rev 1.7
Prompted by a patch from John Carmack to add an an error path when exFAT
is detected on mount to give a more helpful error message.
Returning EINVAL in the existing sanity checks will make mount_msdos(8)
print "not an MSDOS filesystem" when attempting to mount exFAT and
matches historic and documented behaviour.
ok kn@
|
|
the ci_acpicpudev pointer in struct cpu_info. This simplifies matters
when we have lots of cpus.
ok kettenis@
|
|
kstats are identified by a "provider:instance:name:unit" tuple,
where provider and name are strings, and instance and unit are
integers. you can pass tuples as arguments to kstat to select them
for display, eg, to see the rxq and txq stats for the first rings
on an em0 interface, you can run `kstat em0:0:rxq:0 em0:0:txq:0`.
this can be pretty tedious if you want to select a group of stats
quickly though, so there's some wildcard and pattern matching support.
firstly, empty fields in the tuple are wildcarded, eg, if you want
to see all the stats that an mcx0 interface provides then run
`kstat mcx0:::`.
secondly, strings in a tuple (ie, the provider and name fields) are
compared using fnmatch(3) so you can use shell like patterns to
match fields. to expand the last example to all mcx interfaces, you
can run `kstat mcx*:::`.
lastly, you can pass a bare name to match on all kstats with that
name. eg, to see the txq stats for all interfaces, just run
`kstat txq`.
|
|
The ITIMER_VIRTUAL and ITIMER_PROF per-process interval timers are
updated from hardclock(9). If a timer for the parent process is
enabled the hardclock(9) thread calls itimerdecr() to update and
reload it as needed.
However, in itimerdecr(), after entering itimer_mtx, the thread needs
to double-check that the timer in question is still enabled. While
the hardclock(9) thread is entering itimer_mtx a thread in
setitimer(2) can take the mutex and disable the timer.
If the timer is disabled, itimerdecr() should return 1 to indicate
that the timer has not expired and that no action needs to be taken.
ok kettenis@
|
|
|
|
With input from inoguchi@
ok beck@ inoguchi@
|
|
|
|
|
