Age | Commit message (Collapse) | Author |
|
and make it compatible with bsd.lv mandoc and with groff-1.21.
This tweak was originally added for compatibility with groff-1.15,
which is no longer needed.
ok jmc@ kristaps@
|
|
Among other things, this fixes early panics on hppa system which memory size
is exactly 128MB.
Found the hard way and reported by fries@, not reported by beck@
|
|
reported by espie@, not reported by miod@
with and ok shadchin@, ok espie@
|
|
linux bits compiled on i386 by sebastia@, mikeb@ ok
|
|
Found by Jan Klemkow. Thanks!
|
|
Found by Jan Klemkow. Thanks!
|
|
when the macro can change without automatically fixing the comment.
instead add a diagnostic that checks that the biggest cluster size is
always MAXMCLBYTES.
requested by and ok kettenis@
|
|
ok claudio@ henning@ mikeb@
|
|
tech@
|
|
This allows these devices to attach as ugen, so at least we can use some apps,
like gphoto2 to retrieve media.
requested by a few, ok mikeb@
|
|
|
|
|
|
ok dlg claudio
|
|
cluster the generic network stack will be able to give you.
it also recognises that external storage on an mbuf may be bigger than
MCLBYTES. its only when m_pullup or m_pulldown need to allocate
another cluster that they now check the len argument, and now they
do it against MAXMCLBYTES.
this is required for me to do pfsync on jumbo frames as the m_pulldown
for the subregions fail beyond MCLBYTES into the packet.
ok deraadt@ mikeb@ henning@ blambert@
manpage changes ok jmc@
|
|
ok deraadt@ claudio@ blambert@ mikeb@
|
|
of critical structures when it hit a collision. Also, ttyopen is ldisc
0, so it should not be called twice (and furthermore, with the wrong dev_t)
original report from mikeb, ok dlg mikeb and discussed with miod
|
|
if we actually did any work. Otherwise devices sharing this interrupt will
not have their interrupt handler run, possibly leading to the kernel
spinning in the vic(4) interrupt handler.
ok dlg@
|
|
|
|
with every other thing that stores the state id (including other pfsync
messages).
includes improvements to the systat code to consider the creatorid as well
as the state id in its cache to avoid collisions between states created on
different hosts.
tested by me in production and on amd64 talking to sparc64.
ok henning@
|
|
ok mlarkin
|
|
|
|
code instead of testing only the phy. Fixes autoneg on ich9.
From Jonathan Perkin
|
|
either an mbuf leak or a NULL pointer dereference.
ok sthen@ claudio@ dlg@
testing claudio@ dlg@
|
|
pf_state_expires() handled it incorrectly.
discussed with mikeb@
ok henning@
|
|
LLONG_MAX instead of SSIZE_MAX
ok deraadt@
|
|
|
|
getting rid of the (hopefully) last bug in this code.
|
|
lost during update. Originally from claudio, rev1.46.
ok claudio
|
|
Fix the IP ckecksum offloading logic that disables and breaks offloading
if the packet is neither TCP nor UDP because of an erroneous "default" case.
No functional change in the default build because IP checksum offloading
is currently disabled in ix(4).
Tested on 82598 and 82599 (though checksums are still disabled by default).
ok claudio
|
|
accidental race conditions. From Erik Lax, thanks! ok dlg
|
|
|
|
|
|
from bcopy.m4. Fix that.
|
|
|
|
Also fix the return value of memcpy. With these changes, this seems to
work as advertised now.
|
|
|
|
|
|
When transmitting through vlan(4), it will now use the prio value in
pf packet header. When receiving, we save the incoming Cos in the same
place, this gives us the hability to preserve the CoS value across two
different vlan interfaces.
This kills the SIOC[GS]VLANPRIO ioctls and removes the corresponding
buttons from ifconfig(8).
ok henning@ claudio@ mcbride@
|
|
|
|
urtwn0 at uhub0 port 1 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address c4:3d:c7:....
ok gray
|
|
|
|
ok jsg
|
|
connection does not observe the route-to option.
ok dlg mikeb
|
|
pointed out by Julien Crapovich on misc@
ok deraadt mikeb
|
|
skewed at runtime by things like date(1) and ntpd. time_uptime is
monotonic and therefore more useful to compare against.
ok deraadt@ mikeb@
|
|
ok pirofti@
|
|
been done earlier because these new and improved constraints lose bigtime
with gcc3, so be sure to compile your kernel with gcc 4 only if you have
atomic.h 1.10 onwards.
|
|
|
|
|
|
ok mikeb
|