| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
when maxbufspace is larger than INT_MAX / 3. The overflow causes a
hard hang on ia64 when physical memory is sufficiently large (8GB).
|
|
|
|
| |
needed for breakpoints to work.
|
|
|
|
|
|
| |
caches with data caches after writing to memory. This typically
is required to make breakpoints work on ia64 and powerpc. For
those architectures the function is implemented.
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes places where they should be called atomically changing
their locking requirements (both assume per-proc spinlock held) and
introducing rufetchcalc which wrappers both calls to be performed in
atomic way.
Reviewed by: jeff
Approved by: jeff (mentor)
|
|
|
|
| |
Approved by: sat (mentor)
|
|
|
|
|
|
|
|
|
| |
in tcp_outout(). This is currently not strictly necessary but paves
the way to simplify the entire SYN options handling quite a bit.
Clarify comment. No change in effective behavour with this commit.
RFC1323 requires the window field in a SYN (i.e., a <SYN> or
<SYN,ACK>) segment itself never be scaled.
|
|
|
|
|
|
|
|
|
|
| |
and simplify handling of the send/receive window scaling. No
change in effective behavour.
RFC1323 requires the window field in a SYN (i.e., a <SYN> or
<SYN,ACK>) segment itself never be scaled.
Noticed by: yar
|
|
|
|
|
|
| |
time_lock spinlock exported.
Approved by: jeff (mentor)
|
|
|
|
| |
and won't ever send more data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Unsafeness on ruadd() in thread_exit()
- Unatomicity of thread_exiit() in the exit1() operations
This patch addresses these problems allocating p_fd as part of the
process and modifying the way it is accessed.
A small chunk of this patch, resolves a race about p_state in kern_wait(),
since we have to be sure about the zombif-ing process.
Submitted by: jeff
Approved by: jeff (mentor)
|
| |
|
|
|
|
|
|
|
|
|
| |
a timer issues a shutdown and a simultaneous close on the socket
happens. This race condition is inherent in the current socket/
inpcb life cycle system but can be handled well.
Reported by: kris
Tested by: kris (on 8-core machine)
|
| |
|
|
|
|
|
|
|
| |
- Reorder send failed to be in correct order.
- Fixed calulation of init-ack to be right off
mbuf lengths instead of the precalculated value. This
will fix one 64 bit platform issue.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Kill devinfo stuff.
|
|
|
|
|
| |
# looks like there's a chance that uaudio might compile on otherBSD, so leave
# those #defines alone as well as make this change in a compatible way.
|
|
|
|
|
|
| |
Remove bogus bzero/memset
Expand USB_ATTACH_SETUP
Minor nits
|
|
|
|
|
| |
o other bsd defines, there's no way this would work there
o devinfo junk
|
|
|
|
|
|
| |
Kill bogus bzero as necessary.
Minor tidy.
Expand USB_ATTACH_SETUP inline where needed.
|
|
|
|
| |
While I'm here, kill devinfo junk.
|
|
|
|
|
|
|
|
|
|
|
| |
error doing so. It seems an increasing number of phones have this
quirk, and we're not keeping up. There appears to be nothing bad that
happens for non-quirked phones.
Minor cleanups:
o prefer device_printf over printf
o kill devinfo stuff
o minor other preening.
|
|
|
|
|
|
|
| |
need to do it at all anymore. Remove it from here. Expand
USB_ATTACH_SETUP inline now that it is one line and we're moving away
from the compat macros. Remove some bzero calls that turn out not be
be necessary.
|
|
|
|
| |
Submitted by: edwin@
|
|
|
|
|
|
|
|
|
| |
Correct long-standing off-by-one error in -W option.
Submitted by: edwin@
Shorten some long lines. These files are still not completely
style(9) compliant.
|
| |
|
|
|
|
| |
Submitteed by: edwin@
|
|
|
|
|
| |
from an int to a long to avoid printing negative byte and page
counts.
|
|
|
|
|
|
| |
what we print, don't print it anymore. And don't compute it anymore.
And don't malloc/free memory for it anymore. While I'm here, prefer
device_printf where appropriate.
|
|
|
|
|
| |
int anymore. This was causing all sorts of bad behavior when booting a system
with an nve interface present.
|
|
|
|
|
|
| |
mutexes.
Currently we alredy force MUTEX_WAKE_ALL beacause of some problems with the
!MUTEX_WAKE_ALL case (unavioidable priority inversion).
|
|
|
|
|
|
|
|
| |
auditing to be turned on without a kernel recompile, just an rc.conf
option.
Approved by: re (kensmith)
Obtained from: TrustedBSD Project
|
|
|
|
| |
Requested by: pjd@
|
|
|
|
| |
Tested with: md5(1)
|
|
|
|
|
| |
be tuned along with the rest of hostcache parameters.
The new sysctl name is `net.inet.tcp.hostcache.prune'.
|
| |
|
|
|
|
|
|
|
|
|
| |
the value of ph_nhooks to zero, not the address. This removes
extranious calls to pfil_run_hooks (and an rw lock) from the
network stack's critical path when no pfil hooks are active.
Reviewed by: csjp
Sponsored by: Myricom Inc.
|
|
|
|
|
|
|
| |
implementing some of them using existing ones.
- Allow to compile ZFS on all archs and use atomic operations surrounded
by global mutex on archs we don't have or can't have all atomic
operations needed by ZFS.
|
|
|
|
| |
Submitted by: marcel
|
|
|
|
| |
go into userland to improve the chances of people noticing them.
|
|
|
|
|
|
|
| |
algoritm would not go through the proper initialization.
- The initialization was incorrect as well, causing problems in
sat networks with > 1sec RTT
- Get rid of magic numbers in RTT calculations.
|
| |
|
|
|
|
| |
We would like to keep connection after halt.
|
|
|
|
|
| |
- We are in FWBUSINIT state just after SID interrupt.
- Do not pass normal xfers before bus probe is done.
|
|
|
|
|
| |
the bufobj, rather than using VI_LOCK, like what was done with
revision 1.453.
|
|
|
|
| |
otherwise.
|
|
|
|
| |
resetting target and suspending dconschat.
|