| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Reported by: "Ted Unangst" <tedu@coverity.com>
Approved by: rwatson (mentor)
|
|
|
|
|
|
|
|
| |
Introduce d_version field in struct cdevsw, this must always be
initialized to D_VERSION.
Flip sense of D_NOGIANT flag to D_NEEDGIANT, this involves removing
four D_NOGIANT flags and adding 145 D_NEEDGIANT flags.
|
|
|
|
|
|
|
| |
Free approx 86 major numbers with a mostly automatically generated patch.
A number of strategic drivers have been left behind by caution, and a few
because they still (ab)use their major number.
|
|
|
|
|
|
|
|
| |
layering violation. As pointed out, there is much better way to do this.
Sorry guys, I need to find a better way to force reviews.
Requested by: harti, julian, scottl (mentor)
Pointy hat to: pjd
|
|
|
|
|
|
|
|
|
|
| |
It works as follows:
In every 'interval' seconds defined links are checked.
If they are non-active they will not be used by to data transfer.
No response from: julian, archie
Silent on: net@
Approved by: scottl (mentor)
|
|
|
|
|
|
|
|
| |
It'll is required by new failure detection algorithm for ng_one2many(4).
No response from: julian, archie
Silent on: net@
Approved by: scottl (mentor)
|
|
|
|
|
| |
that we can get rid of of all the spl*() calls, because ng_timeout
handles the locking issues.
|
| |
|
| |
|
|
|
|
|
| |
correct some indendation, change __FUNCTION__ to __func__ and remove
a local KASSERT definition.
|
|
|
|
|
|
|
| |
problem here still to be solved: the sockaddr_hci has still a 16 byte
field for the node name. The code currently does not correctly use the
length field in the sockaddr to handle the address length, so
node names get truncated to 15 characters when put into a sockaddr_hci.
|
|
|
|
| |
that also include the trailing \0 byte.
|
|
|
|
|
| |
traffic for non-ethernet hooks. This commit should have been packaged
with the commit to ng_source.c.
|
|
|
|
|
|
|
| |
introducing a START_NOW command. This command does not send
and GET_IFINDEX message downstream (to wait for the response from
the ETHERNET node), but directly starts the sending process. This allows
one to generate traffic as input for any hook on any node.
|
| |
|
|
|
|
|
|
| |
fiddle around with private queues, because their mutex is not
needed. All this processing should be protected by the netgraph
locking.
|
|
|
|
| |
malloc().
|
|
|
|
|
|
|
| |
the netgraph version.
Correct the return type of a function: it wants to return an error
code, so it cannot be void.
|
|
|
|
| |
*SIZ constants that include the trailing \0 byte.
|
|
|
|
| |
(that include the trailing \0) constants instead.
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
| |
and receive FCS-less RFC1490-"bridged" Ethernet packets that are
currently just ignored.
|
|
|
|
| |
detached from the other direction.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a new bpf_mtap2 routine that does the right thing for an mbuf
and a variable-length chunk of data that should be prepended.
o while we're sweeping the drivers, use u_int32_t uniformly when
when prepending the address family (several places were assuming
sizeof(int) was 4)
o return M_ASSERTVALID to BPF_MTAP* now that all stack-allocated
mbufs have been eliminated; this may better be moved to the bpf
routines
Reviewed by: arch@ and several others
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
which means "always stay in the standard mode of PPPoE operation
regardless of any junk floating around."
As the referenced PR stated clearly, the old default setting of 0
was extremely dangerous because it opened a possibility for a
spurious frame not only to put down a single PPPoE node running
FreeBSD, but to plague *every* FreeBSD node in a PPPoE network in
such a way that those nodes would keep poisoning each other until
rebooted simultaneously.
PR: kern/47920
Reviewed by: Gleb Smirnoff <glebius <at> cell.sick.ru>
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
nonstandard. They differ in the values of certain fields in
the PPPoE frame. Previously, ng_pppoe would start in standard
mode, yet switch to nonstandard one upon reception of a single
nonstandard frame. After having done so, ng_pppoe would be unable
to interact with standard PPPoE peers. Thus, a DoS condition
existed that could be triggered by a buggy peer or malicious party.
Since few people have expressed their displeasure WRT this problem,
the default operation of ng_pppoe is left untouched for now. However,
a new value for the sysctl net.graph.nonstandard_pppoe is introduced,
-1, which will force ng_pppoe stay in standard mode regardless of any
bogus frames floating around.
PR: kern/47920
Submitted by: Gleb Smirnoff <glebius <at> cell.sick.ru>
MFC after: 1 week
|
|
|
|
| |
Submitted by: archie
|
| |
|
|
|
|
| |
OK'ed by: archie
|
|
|
|
| |
Reviewed by: julian
|
|
|
|
|
| |
two functions in sys/net/if.c that assume that softc starts with arpcom.)
This makes setting of ethernet address via ifconfig(8) work as expected.
|
|
|
|
| |
Submitted by: Gavin Atkinson <gavin+freebsdc@ury.york.ac.uk>
|
|
|
|
| |
functional change since MTX_DEF happens to be defined as 0.
|
|
|
|
|
|
|
|
|
| |
In practice it seems that in situations of high packet loss the ACK
timeout seems to hit this maximum (perhaps inappropriately, but the
estimation algorithm is not perfect, so apparently it happens). In
any case, 10 seconds is way too high a value so lower to 1 second.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the MAC label referenced from 'struct socket' in the IPv4 and
IPv6-based protocols. This permits MAC labels to be checked during
network delivery operations without dereferencing inp->inp_socket
to get to so->so_label, which will eventually avoid our having to
grab the socket lock during delivery at the network layer.
This change introduces 'struct inpcb' as a labeled object to the
MAC Framework, along with the normal circus of entry points:
initialization, creation from socket, destruction, as well as a
delivery access control check.
For most policies, the inpcb label will simply be a cache of the
socket label, so a new protocol switch method is introduced,
pr_sosetlabel() to notify protocols that the socket layer label
has been updated so that the cache can be updated while holding
appropriate locks. Most protocols implement this using
pru_sosetlabel_null(), but IPv4/IPv6 protocols using inpcbs use
the the worker function in_pcbsosetlabel(), which calls into the
MAC Framework to perform a cache update.
Biba, LOMAC, and MLS implement these entry points, as do the stub
policy, and test policy.
Reviewed by: sam, bms
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
| |
Reviewed by: harti
|
|
|
|
| |
Reviewed by: harti
|
|
|
|
|
|
|
| |
the rest of Netgraph code.
Reviewed by: imp, ru
Approved by: imp (mentor)
|
|
|
|
| |
others in netgraph.
|
|
|
|
|
|
| |
length definitions.
Reminded by: jdp
|
|
|
|
|
|
|
|
|
|
| |
defines for these constants that include the trailing NUL byte. These
new constants have SIZ in their name instead of LEN. As soon as all
consumers in the tree are converted to use the new defines the old
defines will be put under BURN_BRIDGES.
Reviewed by: archie, julian, ru
Approved by: re (in principle)
|
|
|
|
| |
with nge(4).
|
|
|
|
| |
Reviewed by: archie, harti, emax
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
whether or not the isr needs to hold Giant when running; Giant-less
operation is also controlled by the setting of debug_mpsafenet
o mark all netisr's except NETISR_IP as needing Giant
o add a GIANT_REQUIRED assertion to the top of netisr's that need Giant
o pickup Giant (when debug_mpsafenet is 1) inside ip_input before
calling up with a packet
o change netisr handling so swi_net runs w/o Giant; instead we grab
Giant before invoking handlers based on whether the handler needs Giant
o change netisr handling so that netisr's that are marked MPSAFE may
have multiple instances active at a time
o add netisr statistics for packets dropped because the isr is inactive
Supported by: FreeBSD Foundation
|