| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
it will figure out the correct target to handle index and be able to find
things like WWPN, etc.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
calling socantrcvmore_locked() since it will unlock
the lock for you.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
input file before using it.
PR: bin/147275
Submitted by: thomas
MFC after: 1 week
|
|
|
|
|
| |
limit on the number of hardware filters (and thus the amount of TCAM
reserved for filtering).
|
|
|
|
|
|
|
|
| |
Don't leak memory when deleting param from gctl_req.
Reviewed by: marcel
Approved by: mav (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
| |
changes in L2ARC and zfs send.
Approved by: delphij (mentor)
|
|
|
|
|
|
|
|
| |
don't see a race where we unlock to call
the non-locked version and have the socket
go away.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is enabled.
This already worked if without job control.
In either case, this depends on it that a process that terminates due to
SIGINT exits on it (so not with status 1, or worse, 0).
Example:
sleep 5; echo continued
This does not print "continued" any more if sleep is aborted via ctrl+c.
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the timer. This is done by considering the locks
we will destroy and if they are contended we consider
it the same as a reference count being up. Fixing this
appears to cleanup another crash that was appearing with
all the timers where the socket buf lock got corrupted.
2) Fix the sysctl code to take a lot more care when looking
at INP's that are in the GONE or ALLGONE state.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of apitesters.. Basically we end up with attempting
to destroy a lock thats contended on. A cookie echo
arrives at the same time that the close is happening.
The close gets the lock but the cookie echo has already
passed the check for the gone flag and is then locked
waiting on the create lock.. when we go to destroy it
bam. For now we do the timer destroy for all calls
to close.. We can probably optimize this later so that
we check whats being contended on and if there is contention
then do the timer thing. but this is probably safest since
the inp has been removed from all lists and references and
only the timer can find it.. once the locks are released all
other places will instantly see the GONE flag and bail (thats
what the change in sctp_input is one place that was lacking
the bail code).
MFC after: 1 week
|
|
|
|
|
| |
Noted by: bde
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
held by checking the create and inp locks as well.
2) Fix a bug in that when a socket is closed an INIT-ACK
is returned, we do NOT unlock the locked_tcb unless its
different (an unlikely scenario). If we blindly unlock as
we were doing before we can end up unlocking the actual
stcb thats about to be sent down to the free function which
requires the lock be held.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
was setup to do an abortive close an association that was
in the accept_queue could get stuck and never freed. Now
we properly start the kill timer on the socket and turn
off the flag (same thing we do for the graceful close method).
MFC after: 1 week
|
|
|
|
|
|
|
| |
when the gone flag is set. You don't know what locks the
caller has set and there is already a kill timer running.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
optionally with a header if "-h" is passed. Toast CPU time measurement
in the server for now. Remove -C and -T, since we now always report
both connections/sec and Gb/sec.
MFC after: 1 week
Sponsored by: Juniper Networks
|
|
|
|
| |
Submitted by: Andreas Tobler
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
corruption bug where if an ATA command is issued before DMA is started,
data will become available to the controller before it knows what to do
with it. This results in either data corruption or a controller crash.
This patch remedies the problem by adopting the workaround employed
by Linux and Darwin: starting the DMA engine prior to sending the ATA
command.
Observer on: Xserve G5
Reviewed by: mav
MFC after: 1 week
|
|
|
|
|
| |
Requested by: gk (via private mail)
Approved by: delphij (mentor)
|
|
|
|
| |
Submitted by: Hizel Ildar <hizel@vyborg.ru> (via current@)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the page is managed.
Don't set the machine-independent layer's dirty field for the page being
mapped in init_pte_prot(). (The dirty field is only supposed to set when
a mapping is removed or write-protected and the page was managed and
modified.)
Determine whether or not to perform dirty bit emulation based on whether
or not the page is managed, i.e., pageable, not based on whether the page
is being mapped into the kernel address space. Nearly all of the kernel
address space consists of unmanaged pages, so this has neglible impact on
the overhead of dirty bit emulation for the kernel address space. However,
there can also exist unmanaged pages in the user address space. Previously,
dirty bit emulation was unnecessarily performed on these pages.
Tested by: jchandra@
|
|
|
|
|
|
|
| |
so we only hold the iterator lock during
updates to the iterators work.
MFC after: 1 week
|
|
|
|
|
|
| |
error legs.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
buffers it should also reinitialize RX descriptors otherwise some
stale data could be passed to controller. This could end up with
mbuf double free or unexpected NULL pointer dereference in upper
stack. To fix the issue, save loaded buffer's length and
reinitialize RX descriptors with the saved value whenever bge(4)
reuses the loaded RX buffers.
While I'm here, increase the number of RX buffers to 512 from 256.
This simplifies RX buffer handling as well as giving more RX
buffers. Controller supports just fixed number of RX buffers
(i.e. 512) and bge(4) used to rely on hope that our CPU is fast
enough to keep up with the controller. With this change, bge(4)
will use 1MB for RX buffers but I don't think it would cause
problems in these days.
Reported by: marcel
Tested by: marcel
|
|
|
|
|
|
|
| |
Remove uncessary check for error.
Found with: Coverity Prevent(tm)
MFC after: 1 month
|
|
|
|
|
| |
Found with: Coverity Prevent(tm)
MFC after: 1 month
|
|
|
|
|
|
|
| |
add a -P to enable it if it were.
MFC after: 1 week
Sponsored by: Juniper Networks
|
|
|
|
|
| |
Found with: Coverity Prevent(tm)
MFC after: 1 month
|
|
|
|
|
|
| |
past the scrubber.
MFC after: 1 Week
|
|
|
|
| |
MFC after: 1 Week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Fix the alignment of a comment.
2) Fix a BUG where we were NOT paying attention
to the RESEND marking on retransmitting control
chunks.. and worse we were not decrementing the
retran count that could cause us to loop forever.
3) Add in the valdiate_no_lock function on invariants
so that we will really check all ways out to be sure
a lock does not slip out locked.
MFC after: 1 week.
|
|
|
|
|
|
| |
number on sent_queue_retran_cnt.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
1) Makes it so that the INVARIANT function validate nolocks is
available anywhere.
2) Fixes a BUG where a close has been done on a collision socket
and the cookie processing would return leaving a lock held.
MFC after: 1 week
|
|
|
|
|
|
|
| |
had un-accepted assoc's. Basically the assoc (and inp)
would get stuck and never get cleaned up.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
bug but we might as well be clearer.
Found with: Coverity Prevent(tm)
CID: 3981
MFC after: 2 weeks
|
|
|
|
|
| |
Submitted by: alc
MFC after: 8.1-RELEASE
|
|
|
|
| |
Correct a typo in a nearby comment on sparc64.
|
|
|
|
| |
PowerMac 11,2.
|
| |
|
| |
|
|
|
|
|
|
| |
allow consumers of iicbus_transfer() to send messages with repeated starts.
Reviewed by: imp
|
|
|
|
| |
interrupt.
|
|
|
|
|
|
|
|
|
|
|
|
| |
fix. On Apple OpenPICs, the low/high bit of the interrupt sense is only
respected for interrupt 0. We currently erroneously program all OpenPIC
interrupts level high instead of level low by default, which only matters
for some G5 systems where the SATA controllers use IRQ 0.
This change is a quick fix that will be reverted once the effect of
changing the default interrupt sense on embedded systems is known.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
are respected. This fixes loading the Apple onboard audio driver
(snd_ai2s) as a module after boot, which would previously cause a panic.
PR: powerpc/146888
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
context from in-kernel execution of padlock instructions and to handle
spurious FPUDNA exceptions that sometime are raised when doing padlock
calculations.
Globally mark crypto(9) kthread as using FPU.
Reviewed by: pjd
Hardware provided by: Sentex Communications
Tested by: pho
PR: amd64/135014
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FPU/SSE hardware. Caller should provide a save area that is chained
into the stack of the areas; pcb save_area for usermode FPU state is
on top. The pcb now contains a pointer to the current FPU saved area,
used during FPUDNA handling and context switches. There is also a
facility to allow the kernel thread to use pcb save_area.
Change the dreaded warnings "npxdna in kernel mode!" into the panics
when FPU usage is not registered.
KPI discussed with: fabient
Tested by: pho, fabient
Hardware provided by: Sentex Communications
MFC after: 1 month
|
|
|
|
|
|
|
| |
It is obvious that it isn't used, but both clang and Coverity talk about it.
Found with: Coverity Prevent(tm)
CID: 8066
|
|
|
|
| |
Found with the clang checker.
|
| |
|
|
|
|
|
|
|
| |
It was mostly harmless since strftime() only used %a and %b anyway.
Found with: Coverity Prevent(tm)
CID: 7769
|