| Age | Commit message (Collapse) | Author |
|---|
|
number in the name to simplify identifying the card in dmesg. OK dms
|
|
function, which is additionally exported for use by others.
It will be needed by smtpd's SSL module when the SMTP client code
is changed to replace libevent's evbuffers with our msgbuf_* API.
ok gilles@ henning@ guenther@ eric@
|
|
mode and/or E-BGP multihop. Ok and suggestions from claudio@
|
|
|
|
|
|
cpu_info pointer array, cpu_info iterator, cpu_number() implementation added.
constraint modifier fixed in lock.h to output correct assembly.
calling proc_trampoline_mp in exception.S.
|
|
|
|
through the registers of TSEC1. Makes the first ethernet port on the rb600
usable.
|
|
Update the expected answers accordingly. Found by david, OK fgsch
|
|
independent LINK_STATE_DESCRIPTIONS. Code is now more or less a one to
one copy of get_linkstate() in route/route.c.
OK henning, michele, sthen, deraadt
|
|
of the if_media dance. Simplifies the code nicely.
OK henning, sthen, michele, deraadt
|
|
if_media. This makes link state tracking a lot easier as there is no need
to convert if types to if_media types, etc. Additionally this allows us
to extend the link states to include states tracked on higher protocol layers.
gre(4) keepalives packets, bfd and udld can be implemented without ugly hacks.
OK henning, michele, sthen, deraadt
|
|
|
|
also reported upstream to dhcp dash bugs at isc dot org
|
|
problem reported by martynas@. this bug has been there a long
time (r1.61), but sloppy RIRB handling was hiding it ...
|
|
|
|
in SCR_GRAPHICS mode; spotted by martynas@
|
|
with it which became extremely annoying with what mpath wants to
do.
the major change is a new interface for submitting scsi commands.
previously the only way for drivers like sd, cd, st, etc to push
commands onto the hardware was via scsi_scsi_cmd(). the problem
with scsi_scsi_cmd is that it doesnt tell the caller if the command
failed, was queued, or completed unless you shoved a buf down with
it. this is important for mpath which wants to know what the physical
path to the device did so it can report it back to the midlayer
which called it.
this provides a new api which lets drivers like cd/sd/st/mpath etc
allocate an xs, fill it in, and provide a completion routine which
the midlayer will call with the state of the command when it is
finished with it. the caller is then responsible for freeing the
xs.
from the hba side of thing, the return code from the scsi_cmd
entrypoint is largely ignored now, and it is now always the
responsibility of the hba driver to call scsi_done when it has
completed the io, rather than returning COMPLETE and expecting the
midlayer to do it for you.
i have emulated scsi_scsi_cmd on top of this new api so existing
users of it will continue to work. sd(4) has been reworked to use
the new api directly to both demonstrate its use and test that the
new api actually does work.
this diff was mostly written in a day at f2k9. thanks to miod for poking
through hba drivers to help mitigate against fallout from the change to
the COMPLETE semantic. this has been reviewed by krw who didnt spot
anything wrong.
thanks to dave del debbio for testing.
ok deraadt@
|
|
the number of bytes currently read into the sm_data array.
Problem found by recent version of gcc.
|
|
check their return values in the ATA_S_COMPLETE ioctl handler.
dlg@ agrees.
|
|
|
|
with m_tag_copy_chain() failures.
Use m_defrag() to eliminate hand rolled defragging of mbufs and
some uses of M_DUP_PKTHDR().
Original diff from thib@, claudio@'s feedback integrated by me.
Tests kevlo@ claudio@, "reads ok" blambert@
ok thib@ claudio@, "m_defrag() bits ok" kettenis@
|
|
and ok kettenis@
|
|
|
|
out-of-bounds array access later on.
ok drahn@, dms@
|
|
|
|
operations, so we do compression in there as well.
|
|
|
|
function.
|
|
than the hardcoded ones we used before. Replace a few magic numbers with
#defines while I'm there. Based on suggestions from dms@.
|
|
don't crash if we unmask a preconfigured interrupt.
|
|
|
|
|
|
|
|
|
|
This is not as strict as various RFCs want it, but we can make it
more granular later. For now, let all mails flow by using the
maximum of all limits found in the RFCs.
ok gilles@
|
|
new windows.
|
|
deduced from the buffer size prior and after evbuffer_readline() call. the
problem is that this accounts for the characters which evbuffer_readline()
removed and we do not know how many they were (\n, \r\n ..). fix just does
a strlen() call of line which is a bit slower but way safer.
This could very well fix the broken headers issue some people reported
|
|
|
|
|
|
- add a new stats counter to distinguish between command lines which
exceeded the limit and data lines which exceeded the limits
|
|
the one with the lowest association.
|
|
and into it's own function, azalia_get_ctrlr_caps()
|
|
while being less error prone
|
|
behaviour.
|
|
- re-order client options in usage() to match server options
and the manual, as suggested by jmc.
ok jmc@
|
|
and continue operation afterwards. If we can't flush immediately, we will
undo the operation and return EAGAIN to wsdisplay (like we do already for
the xfer queue).
This allows us to set higher resolutions (tested up to 1280x1024) without
bumping the command buffer or xfer buffer memory further.
|
|
suggested by maja@, ok by kettenis@
|
|
ok by kettenis@
|
|
and filter rules, because we no longer have translation rules.
Pointed out by Mitja Muzenic, ok henning@
|
