| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
order to add $FreeBSD$ tags, which helps mergemaster better manage
updating them.
Requested by: several
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
|
|
| |
provide better debugging information.
Prefer explicit comparison to NULL for tcpcb pointers rather than
treating them as booleans.
MFC after: 1 month
|
|
|
|
|
|
| |
and is 0 by accident.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
in the man page update.
PR: docs/94938
Submitted by: Ed Schouten <ed@fxq.nl>
MFC After: 3 days
|
| |
|
|
|
|
|
|
|
|
| |
fixup IP checksum when modifying IP header fields
PR: kern/93849
Obtained from: OpenBSD
MFC after: 3 days
|
|
|
|
| |
error if it's NULL, as so_pcb != NULL is now an invariant.
|
|
|
|
|
|
|
| |
completion for unsupported commands doesn't abort.
Reviewed by: nate
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Introduce invariant that all IPX/SPX sockets will have valid so_pcb
pointers to ipxpcb structures, and that for SPX, the control block
pointer will always be valid. Don't attempt to free the socket or
pcb at various odd points, such as disconnect.
- Add a new ipxpcb flag, IPXP_DROPPED, which will be set in place of
freeing PCB's so that this invariant can be maintained. This flag
is now checked instead of a NULL check in various socket protocol
calls.
- Introduce many assertions that this invariant holds.
- Various pieces of code, such as the SPX timer code, no longer needs
to jump through hoops in case it frees a PCB while running.
- Break out ipx_pcbfree() from ipx_pcbdetach(). Likewise
spx_pcbdetach().
- Comment on some SMP-related limitations to the SPX code.
- Update copyrights.
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
of its allocations fails. Allocate the ipxp last so as to avoid having
to free it if another allocation goes wrong.
Normalize retrieval of ipxp and cb from socket in spx_sp_attach(), and
add assertions.
MFC after: 1 month
|
|
|
|
|
|
| |
about to free the mbuf in the spx_input() error path.
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
especially reads of spx header structures, which will now be cached
in the stack until they can be copied out after releasing the lock.
Panic if a bad socket option direction is passed in by the caller.
MFC after: 1 month
|
|
|
|
|
|
| |
unrecognized timer is passed into the function.
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
Make the kernel side of FAST_IPSEC not depend on the shared
structures defined in /usr/include/net/pfkeyv2.h The kernel now
defines all the necessary in kernel structures in sys/netipsec/keydb.h
and does the proper massaging when moving messages around.
Sponsored By: Secure Computing
|
|
|
|
| |
- Remove trailing space.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A) Fibre Channel Target Mode support mostly works
(SAS/SPI won't be too far behind). I'd say that
this probably works just about as well as isp(4)
does right now. Still, it and isp(4) and the whole
target mode stack need a bit of tightening.
B) The startup sequence has been changed so that
after all attaches are done, a set of enable functions
are called. The idea here is that the attaches do
whatever needs to be done *prior* to a port being
enabled and the enables do what need to be done for
enabling stuff for a port after it's been enabled.
This means that we also have events handled by their
proper handlers as we start up.
C) Conditional code that means that this driver goes
back all the way to RELENG_4 in terms of support.
D) Quite a lot of little nitty bug fixes- some discovered
by doing RELENG_4 support. We've been living under Giant
*waaaayyyyy* too long and it's made some of us (me) sloppy.
E) Some shutdown hook stuff that makes sure we don't blow
up during a reboot (like by the arrival of a new command
from an initiator).
There's been some testing and LINT checking, but not as
complete as would be liked. Regression testing with Fusion
RAID instances has not been possible. Caveat Emptor.
Sponsored by: LSI-Logic.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
is derived from the phrase 'MegaRAID Firmware Interface' used by LSI. This
driver provides a block interface to logical disks on the card and a minimal
management device. It is MPSAFE, INTR_FAST, and 64-bit capable.
Thanks to Dell for providing hardware to test with and IronPort for
sponsoring the work.
Sponsored by: Dell, Ironport
MFC After: 3 days
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
using sscanf and truncating the start/end entries by writing them with a
32 bit int descriptor (%x). The upper bytes of the 64 bit vm_offset_t
variables (for little endian machines) were uninitialized. For big endian
machines, things would have been worse because it was storing the 32 bit
value in the upper half of the 64 bit variable. I've changed it to use
%lx and long types. That should work on all our platforms.
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 day
|
|
|
|
|
|
|
|
| |
greater than the size we autosized. Without this fix, systems with
drives under 10GB can end up with very small /usr partitions...
Broken since: January 2002
Tripped over by: simon
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
determine its value at run time according to other relevant values. This
avoids the creation of runs that are incompletely utilized, as long as
pagesize isn't too large (>32kB, given the current RUN_MIN_REGS_2POW
setting).
Increase the size of several structure bitfields in arena_run_t in order
to avoid integer overflow in the case that a run's header does not overlap
with the space that is usable as application allocation regions. Given
the tiny_min_2pow change, this fix has no additional impact unless
pagesize is >32kB.
Reported by: kris
|
|
|
|
|
|
|
| |
reason compiled fine here. I may be running with other include file
changes locally.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
specified wins to make their interaction less confusing.
|
|
|
|
|
|
|
|
|
| |
flag to use a time other than modtime (-c, -u, or -U), the output would
actually be sorted by the specified time rather than size. This does
alter the behavior in the case where both -S and -t are specified. Now,
-S is always preferred. Previously, -t was preferred if one of -c, -u, or
-U was specified, and -S was preferred otherwise. Perhaps -S and -t should
override each other (last one specified wins).
|
| |
|
|
|
|
|
|
|
| |
sorting.
Submitted by: Andrzej Tobola ato at iem dot pw dot edu dot pl
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
being committed:
- Wrap comments more evenly on right border.
- Clean up braces.
Also, along similar lines:
- Assert some pointers are non-NULL before dereferencing them.
- Remove one assertion that looks, on face value, poor.
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
|
|
|
| |
socket also supports the voltage. Some XV cards have appeared on the
scene (or cards that report they support XV), and in older machines
that have sockets that do not support XV, we were bogusly trying to
power them at XV rather than at 3.3V. Now, power up the card at the
lowest voltage supported by both the card and the socket.
MFC After: 3 days
|
|
|
|
| |
amoung others.
|
|
|
|
|
|
|
| |
If a tail queue is empty the return value of TAILQ_LAST is not
undefined, it is NULL.
Submitted by: Ruslan Ermilov <ru@FreeBSD.org>
|
| |
|
| |
|
| |
|
|
|
|
| |
to 1998 every reboot.
|
|
|
|
|
|
|
|
| |
cam.ko are modules so that aha.ko's undefined symbols can be satisfied by
cam.ko.
Sumitted by: nork
Reviewed by: scottl
|
|
|
|
| |
106). Fix the comment to reflect this.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
it has less overhead.
2. Avoid scheduling task if maximum number of I/O threads is reached.
|