| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o instead of a list of mbufs use a list of m_tag structures a la openbsd
o for netgraph et. al. extend the stock openbsd m_tag to include a 32-bit
ABI/module number cookie
o for openbsd compatibility define a well-known cookie MTAG_ABI_COMPAT and
use this in defining openbsd-compatible m_tag_find and m_tag_get routines
o rewrite KAME use of aux mbufs in terms of packet tags
o eliminate the most heavily used aux mbufs by adding an additional struct
inpcb parameter to ip_output and ip6_output to allow the IPsec code to
locate the security policy to apply to outbound packets
o bump __FreeBSD_version so code can be conditionalized
o fixup ipfilter's call to ip_output based on __FreeBSD_version
Reviewed by: julian, luigi (silent), -arch, -net, darren
Approved by: julian, silence from everyone else
Obtained from: openbsd (mostly)
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a common lock. This change avoids a deadlock between snapshots when
separate requests cause them to deadlock checking each other for a
need to copy blocks that are close enough together that they fall
into the same indirect block. Although I had anticipated a slowdown
from contention for the single lock, my filesystem benchmarks show
no measurable change in throughput on a uniprocessor system with
three active snapshots. I conjecture that this result is because
every copy-on-write fault must check all the active snapshots, so
the process was inherently serial already. This change removes the
last of the deadlocks of which I am aware in snapshots.
Sponsored by: DARPA & NAI Labs.
|
| |
|
|
|
|
|
|
|
| |
in the UDP RPC client code. As a side-effect, this fixes some bugs
that might prevent the RPC call from ever timing out for example
if the server keeps responding with the wrong xid. This could
probably be simplified further by using the EVFILT_TIMER filter.
|
|
|
|
|
| |
PR: 41375
Approved by: joe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of KBDIO_DEBUG which may be defined in the kernel config (as it is in NOTES).
This kind of bug is a _really_ horribly thing as we end up with one bit
of code thinking a particular structure is 136 bytes and another that it
is only 112 bytes.
Ideally all places would remember to #include the right "opt_foo.h" file,
but I think in practice file containing the variable sized struct should
#include it explicitly as a precaution.
Detected by: FlexeLint
|
|
|
|
|
|
| |
This fixes a divide by zero in fdisk(8)
Reviewed by: phk
|
|
|
|
|
|
|
|
|
|
|
|
| |
to be administratively disabled as needed on UFS/UFS2 file systems. This
also has the effect of preventing the slightly more expensive ACL code
from running on non-ACL file systems, avoiding storage allocation for
ACLs that may be read from disk. MNT_ACLS may be set at mount-time
using mount -o acls, or implicitly by setting the FS_ACLS flag using
tunefs. On UFS1, you may also have to configure ACL store.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
| |
new FreeBSD emulation, vec, and output format.
|
| |
|
|
|
|
|
|
| |
RFC2407/IANA assignment. This change breaks binary
compatibility. So, you need to recompile IPsec related
applications.
|
|
|
|
| |
installation guide that refers to it.
|
|
|
|
|
|
|
|
| |
as a regular package, not as a bunch of tarballs in a special
directory on the CDs.
PR: 43977
Submitted by: Brian Candler <B.Candler@pobox.com>
|
| |
|
|
|
|
| |
Found by: FlexeLint.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
automatically set MNT_MULTILABEL in the mount flags.
If FS_ACLS is set in a UFS or UFS2 superblock, automatically
set MNT_ACLS in the mount flags.
If either of these flags is set, but the appropriate kernel option
to support the features associated with the flag isn't available,
then print a warning at mount-time.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
| |
"I think you're right" by: jake
|
|
|
|
|
|
|
|
|
|
|
| |
Ignoring a NULL dev in device_set_ivars() sounds wrong, KASSERT it to
non-NULL instead.
Do the same for device_get_ivars() for reasons of symmetry, though
it probably would have yielded a panic anyway, this gives more precise
diagnostics.
Absentmindedly nodded OK to by: jhb
|
|
|
|
| |
Spotted by: FlexeLint
|
|
|
|
| |
Spotted by: FlexeLint
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs
|
|
|
|
|
|
|
| |
inspecting a superblock.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
|
|
|
| |
accidentally lost in the previous revision.
Submitted by: bde
Pointy hat to: jhb
|
|
|
|
| |
Approved by: deischen
|
|
|
|
| |
err().
|
|
|
|
|
|
|
|
|
| |
I introduced a style problem when I sorted 'a' before 'A'; our
preferred order sorts 'A' first. Correct.
Use .Cm instead of .Ar.
Submitted by: bde
|
|
|
|
|
| |
Submitted by: "Stewart MacLund" <sundie@lunaticfringe.org>
MFC after: 1 week
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
: 2002-10-14 Werner LEMBERG <wl@gnu.org>
:
: * src/roff/troff/node.cc (troff_output_file::put_char_width,
: troff_output_file::put_char, troff_output_file::fill_color,
: troff_output_file::glyph_color): Handle case where color pointer
: is null.
This paniced troff(1) attempting to format the vinum(4) manpage.
|
| | |
|
| |
| |
| |
| |
| | |
Obtained from: NetBSD
MFC after: 1 week
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
were improperly relocated due to faulty logic in lookup_fdesc()
in elf_machdep.c. The symbol index (symidx) was bogusly used for
load modules other than the one the relocation applied to. This
resulted in bogus bindings and consequently runtime failures.
The fix is to use the symbol index only for the module being
relocated and to use the symbol name for look-ups in the
modules in the dependent list. As such, we need a function to
return the symbol name given the linker file and symbol index.
|
| | |
|
| |
| |
| |
| |
| |
| | |
print them with %p. Cast to unsigned long and print with %#lx.
Discussed with: bde
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
'lpc topq' are in the log message for revision 1.2 of lpc/movejobs.c".
However, those details were mistakenly force-committed as revision 1.2
of common_source/matchjobs.c. This forced-commit is just to add the
expected revision 1.2 here, as a pointer to the actual details. See
http://cvsweb.freebsd.org/src/usr.sbin/lpr/common_source/matchjobs.c ,
revision 1.2.
|
| |
| |
| |
| | |
in more than just <sys/types.h>.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
processes forked with RFTHREAD.
- Use a goto to a label for common code when exiting from fork1() in case
of an error.
- Move the RFTHREAD linkage setup code later in fork since the ppeers_lock
cannot be locked while holding a proc lock. Handle the race of a task
leader exiting and killing its peers while a peer is forking a new child.
In that case, go ahead and let the peer process proceed normally as the
parent is about to kill it. However, the task leader may have already
gone to sleep to wait for the peers to die, so the new child process may
not receive a SIGKILL from the task leader. Rather than try to destruct
the new child process, just go ahead and send it a SIGKILL directly and
add it to the p_peers list. This ensures that the task leader will wait
until both the peer process doing the fork() and the new child process
have received their KILL signals and exited.
Discussed with: truckman (earlier versions)
|
| |
| |
| |
| |
| | |
p_leader field is not protected by the proc lock but is only set during
fork1() by the parent process and never changes.
|
| |
| |
| |
| |
| |
| |
| |
| | |
homerolling our own version.
- Rename the enum for memsize from ISA_IVAR_MSIZE to ISA_IVAR_MEMSIZE
since using 'MSIZE' in the macro invocation of ISA_ACCESSOR() conflicts
with the 'MSIZE' kernel option. The accessor function is still
isa_get_msize().
|
| |
| |
| |
| | |
hasn't been filled in for ages.. Nuked.
|
| |
| |
| |
| |
| |
| | |
as spl replacements, but you cant sleep while holding mutexes.
This change has been made on many other drivers.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
or fifo in UFS2, the normal ufs_strategy routine needs to be used
rather than the spec_strategy or fifo_strategy routine. Thus the
ffsext_strategy routine is interposed in the ffs_vnops vectors for
special devices and fifo's to pick off this special case. Otherwise
it simply falls through to the usual spec_strategy or fifo_strategy
routine.
Submitted by: Robert Watson <rwatson@FreeBSD.org>
Sponsored by: DARPA & NAI Labs.
|
| |
| |
| |
| |
| | |
Cleanup my earlier de-__P sweep and remove whitespace between function
names and paramters.
|
| | |
|
| |
| |
| |
| | |
Sponsored by: DARPA & NAI Labs.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It must be removed because it is done without the pipe being locked
via pipelock() and therefore is vulnerable to races with pipespace()
erroneously triggering it by temporarily zero'ing out the structure
backing the pipe.
It looks as if this assertion is not needed because all manipulation
of the data changed by pipespace() _is_ protected by pipelock().
Reported by: kris, mckusick
|
| |
| |
| |
| | |
Spotted by: jhb
|
| |
| |
| |
| |
| |
| | |
o Add comment about ipc_perm's members.
o Add some visibility conditionals for non-standard extentions.
o Remove a comment about ftok() not belonging.
|