| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
should be applied. the SA of AH transport could not be selected
from the SAD because of this bug.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
SPDUPDATE doesn't depend on whether there is a SP or not.
This change makes `generate_policy on' of racoon work.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
- Report destination address of a P2P link when servicing
routing socket messages.
- Report interface name, address, and destination address
of a P2P link when servicing NET_RT_{DUMP,FLAGS} sysctls.
Part of CSRG revision 8.6 coresponds to revision 1.12.
CSRG revision 8.7 corresponds to revision 1.15.
|
| |
|
| |
|
|
|
|
| |
Revision 1.59 corresponded to CSRG revision 8.5.
|
|
|
|
| |
and first hunk of revision 1.76 corresponded to CSRG revision 8.3.
|
| |
|
|
|
|
| |
since that's always true for this loop.
|
|
|
|
|
|
| |
it appears to break at least the ToPIC 100.
Submitted by: Mark Santcroos <marks@ripe.net>
|
| |
|
|
|
|
|
| |
been misled to believe by unknown parties. It probably *should* be an option,
but the runtime value is controlled by a tunable, which Ought To Be Enough.
|
|
|
|
| |
available index.
|
|
|
|
|
|
|
| |
interface in the middle is if_detach()'d). Return (and handle)
ENOENT when the ifmib(4) is accessed for a nonexistent interface.
MFC after: 14 days
|
|
|
|
| |
seconds instead of leaving the uptime field blank.
|
| |
|
|
|
|
| |
Reviewed by: ken@kdm.org
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
spin in a loop eating CPU time. This bug has existed since the
TI-RPC import. The problem is that we should only enter the select
loop if at least one TCP server was started. Fix this by having
the master nfsd become a UDP server itself if there are no TCP
servers.
Also improve/correct the code for cleaning up slave nfsd processes
and unregistering with rpcbind when the master nfsd exits.
One issue that remains open is that if a slave nfsd dies, then all
nfsds will shut down. This is because nfssvc() in the master nfsd
returns 0 when the master nfsd receives a SIGCHLD.
Submitted by: tmm
|
| |
|
|
|
|
| |
Submitted by: sheldonh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the normal interrupt handler (npx_intr()) instead of a special
probe-time interrupt handler, although this causes problems due to
the bus_teardown_intr() not actually even tearing down the interrupt
(these problems were avoided by doing interrupt attachment for the
special interrupt handler directly). Fixed minor bitrot in comments.
The reason for the npxprobe()/npxprobe1() split mostly went away at
about the same time it was made (in 1992 or 1993 just before the
beginning of history). 386BSD ran all probes with interrupts completely
masked, and I didn't want to disturb this when I added an irq probe
to npxprobe(). An irq (not necessarily npx) must be acked for at least
external npx's to take the cpu out of the wait state that it enters
when an npx error occurs, so the probe must be done with a suitable
irq unmasked. npxprobe() went to great lengths to unmask precisely
the npx irq.
Running probes with all interrupts masked was never really needed in
FreeBSD, since FreeBSD always masked interrupts well enough using
splhigh(), but it wasn't until rev.1.48 (1995/12/12) of autoconf.c
that all probes were run with CPU interrupts enabled. This permits
npxprobe() to probe its irq using normal interrupt resources. Note
that most drivers still can't depend on this. It depends on the
interrupt handler being fast and the irq not being shared.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lost when the buggy code goes away completely:
- don't assume that the npx irq number is >= 8. Rev.1.73 only reversed
part of the hard-coding of it to 13 in rev.1.66.
- backed out the part of rev.1.84 that added a highly confused comment
about an enable_intr() being "highly bogus". The whole reason for
existence of npxprobe() (separate from the main probe, npxprobe1())
is to handle the complications to make this enable_intr() safe.
- backed out the part of rev.1.94 that modified npxprobe(). It mainly
broke the enable_intr() to restore_intr(). Restoring the interrupt
state in a nested way is precisely what is not wanted here. It was
harmless in practice because npxprobe() is called with interrupts
enabled, so restoring the interrupt state enables interrupts. Most
of npxprobe() is a no-op for the same reason...
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
devices to fail to proberly initialize at boot..
|
|
|
|
|
| |
based on the size of physical memory. This should eliminate the tweaking
needed for larger memory configurations.
|
|
|
|
|
| |
magnitude. Geez, this is Unix, what is with the arbitrary needless
constants.
|
|
|
|
|
|
|
| |
directly to the native syscall, because no filename handling
needs to be done.
Tested by: Martin Blapp <mb@imp.ch>
|
|
|
|
|
|
|
|
|
| |
argument names match those on Alpha.
o Map the fchown directly to FreeBSD. Since the old version of
fchown is also mapped to the native fchown, give the new one
type NODEF.
Tested by: Martin Blapp <mb@imp.ch>
|
|
|
|
|
|
| |
with strlcpy(3).
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
| |
passed to swap_pager_strategy(). Instead, use a field reserved for drivers
and initialize it before usage.
Reviewed by: dillon
|
|
|
|
|
|
| |
on -arch and cvs-all.
Reviewed by: dillon
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to work, but haven't really due to subtle differences in structs etc.
This is still not perfect (some ioctls are still known not to work, while
others haven't been tested at all), but it's enough to get Debian's ifconfig
to produce relatively sane output.
More work will be needed to get all ioctls (or at least a reasonable subset)
working, and to support the Cisco Aironet config tool mentioned in the PR.
PR: 26546
Submitted by: Doug Ambrisko <ambrisko@ambrisko.com>
|
|
|
|
|
|
| |
PR: bin/28116
Submitted by: Valentin Nechayev <netch@netch.kiev.ua>
MFC in: 1 week
|
|
|
|
|
|
| |
longer happens as a side effect of calling npxsave.
Reviewed by: peter, bde
|
|
|
|
|
| |
defines it as a short. Change that to an array of one short so that FreeBSD's
ifr_flags macro will work (it evaluates to ifr_ifru.ifru_flags[0]).
|
|
|
|
|
| |
to 10Mbps. RFC 2863 says: "For a sub-layer which has no concept
of bandwidth, [ifSpeed] should be zero."
|
|
|
|
|
| |
cope with a few interface changes required by the ia64. In particular,
function pointers on ia64 need special treatment in rtld.
|
|
|
|
|
| |
Prompted by: dd
MFC after: 2 weeks
|
|
|
|
|
|
| |
PR: 31215
Submitted by: Stephane Marzloff <secrer@le-bar.org>
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|