| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
keep the locking and solve the real problem.
|
|
|
|
| |
did anything, so this commit should be considered a NO-OP.
|
|
|
|
|
|
| |
@sys/dev/acpica/acpi_pci_link.c:153" panic by backing out rev 1.37 in the SMP
case. It appears that on a dual-proc machine the assertions in the rev 1.37
commit log hold true.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce domain_init_status to keep track of the init status of the domains
list (surprise). 0 = uninitialized, 1 = initialized/unpopulated, 2 =
initialized/done. Higher values can be used to support late addition of
domains which right now "works", but is potential dangerous. I choose to
only give a warning when doing so.
Use domain_init_status with if_attachdomain[1]() to ensure that we have a
complete domains list when we init the if_afdata array. Store the current
value of domain_init_status in if_afdata_initialized. This way we can update
if_afdata after a new protocol has been added (once that is allowed).
Submitted by: se (with changes)
Reviewed by: julian, glebius, se
PR: kern/73321 (partly)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
call net_add_domain(). Calling this function too early (or late) breaks
assertations about the global domains list.
Actually it should be forbidden to call net_add_domain() outside of
SI_SUB_PROTO_DOMAIN completely as there are many places where we traverse
the domains list unprotected, but for now we allow late calls (mostly to
support netgraph). In order to really fix this we have to lock the domains
list in all places or find another way to ensure that we can safely walk the
list while another thread might be adding a new domain.
Spotted by: se
Reviewed by: julian, glebius
PR: kern/73321 (partly)
|
|
|
|
| |
lines while here.
|
|
|
|
| |
Pointy hat: njl from nskyline_r35 at yahoo com
|
| |
|
|
|
|
| |
but allows a "nodev" in /etc/fstab, etc.
|
|
|
|
|
| |
anyway and for some reason, witness seems confused about what's already
locked and triggers a false panic.
|
|
|
|
|
|
|
|
| |
and the sizeof operator, missing empty lines, void casts, extra empty lines.
Checked by: diff on make *.o lst.lib/*.o
Submitted by: Max Okumoto <okumoto@soe.ucsd.edu> (partly)
|
|
|
|
| |
Requested by: ru
|
|
|
|
|
| |
Stumbled upon by: markus
MFC after: 3 days
|
|
|
|
|
|
|
| |
versions of the structure definition for this: one with const char
pointers, because otherwise gcc won't let us initialize the fields with
constant strings, and one without the const, because we need to work
with the structure.
|
|
|
|
|
| |
to the CVS-Meisters x-mode just happens to work, but is not guaranteed to
do so. Try to be on the safe side.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lock collision.
2. Fix two race conditions. One is between _umtx_unlock and signal,
also a thread was marked TDF_UMTXWAKEUP by _umtx_unlock, it is
possible a signal delivered to the thread will cause msleep
returns EINTR, and the thread breaks out of loop, this causes
umtx ownership is not transfered to the thread. Another is in
_umtx_unlock itself, when the function sets the umtx to
UMTX_UNOWNED state, a new thread can come in and lock the umtx,
also the function tries to set contested bit flag, but it will
fail. Although the function will wake a blocked thread, if that
thread breaks out of loop by signal, no contested bit will be set.
|
|
|
|
|
| |
stubs that at least handle the stack correctly. This makes it much easier to
experiment with loader scripts from userland.
|
|
|
|
|
|
| |
the semantic of Lst_Datum which formerly returned NULL when the argument
node was NULL. There was only one place in the source that relied on this
so change that place.
|
|
|
|
|
|
|
|
|
| |
observations lead me to believe that the convetion for pc98 boot
loaders is to have a jump unstruction, followed by a string, followed
by code. The jump usually doesn't have a nop after it and usually the
string is NUL terminated, but Grub/98 breaks both of these rules.
# I looked for, but failed to find the Minux boot blocks for PC-9801 port.
|
|
|
|
|
| |
MSR in kernel mode. Redefine PSL_USERSET in terms of this by or'ing
in PSL_PR.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
512. If I had an audio cdrom in my cd player when I booted my system,
I'd get a panic from geom because you can't read 8192 bytes from an
audio cdrom.
Remove XXX comment about IPL1 and replace it with some information
from my soon to be published web page on the pc98 disk layout. The
IPL1 test was the result of an observation of a disk with FreeBSD's
boot0 program. It was testing part of an area what appears to be
reserved for a boot loader name, which comes after a jump over this
area. I don't yet know if it is required to be any specific jump
instruction, or if the destination has to be location 11. [1]
[1] FreeBSD Press No. 13, page 115, poorly translated by myself. The
picture there shows offset 8 as the destination of the jump, but
FreeBSD's boot0 program has three padding NULs after the IPL1 name and
uses a 16-bit 'jmp' instruction.
|
|
|
|
|
|
|
|
|
|
|
|
| |
resource lists. It used to be sized based only on _CRS, hence _PRS could
perform an out-of-bounds access if it was larger (i.e., when there are
dependent functions). Add asserts to detect this case. Note, this is
only a temporary fix and I believe _PRS and _CRS should have separate
arrays.
Also, fix a typo where the wrong irq was being check for the APIC case.
Submitted by: tegge
|
| |
|
|
|
|
| |
cpu 0. Also, restructure cpu_reset to be cleaner (no functional change.)
|
| |
|
| |
|
|
|
|
| |
for libgdb and should do so here as well.
|
|
|
|
|
| |
possible, like on i386. Registers are handled differently for caller
vs callee saved registers.
|
|
|
|
| |
choice because it is so in sync with stathz (128hz or 4096hz etc).
|
| |
|
|
|
|
|
| |
eliminate the evil cpu_reset_proxy code now that it will never be
activated. i386 should pick this up as well.
|
|
|
|
|
|
|
|
|
| |
to do a window update to the peer (thru an ACK) from soreceive()
itself. TCP will do that upon return from the socket callback.
Sending a window update from soreceive() results in a lock reversal.
Submitted by: Mohan Srinivasan mohans at yahoo-inc dot com
Reviewed by: rwatson
|
|
|
|
|
|
|
|
| |
soreceive(), then pass in M_DONTWAIT to m_copym(). Also fix up error
handling for the case where m_copym() returns failure.
Submitted by: Mohan Srinivasan mohans at yahoo-inc dot com
Reviewed by: rwatson
|
|
|
|
|
|
|
| |
in the error cases, causing panics.
Submitted by: Mohan Srinivasan mohans at yahoo-inc dot com
Reviewed by: rwatson
|
|
|
|
|
|
|
|
|
| |
that the exclusive lock is already held, then we call panic. Don't
clobber internal lock state before panic'ing. This change improves
debugging if this case were to happen.
Submitted by: Mohan Srinivasan mohans at yahoo-inc dot com
Reviewed by: rwatson
|
|
|
|
|
| |
PR: docs/74529
Submitted by: Jason Bacon <bacon at smithers dot neuro dot mcw dot edu>
|
|
|
|
| |
that they are equivalent.
|
|
|
|
|
| |
Found by: Pawel Worach and Daniel Hartmeier
Submitted by: Mohan Srinivasan mohans at yahoo-inc dot com
|
|
|
|
|
|
|
|
| |
Add ``disable NAS-IP-Address'' and ``disable NAS-Identifier'' options to
support pre-rfc2865 RADIUS servers.
This pushes our enable/disable items over the 32 bit limit, so reoganise
things to allow a bunch more options.
Go to version 3.4.1 so that any compatability problems can be identified.
|
|
|
|
| |
internal variables as well to reflect the change.
|
|
|
|
|
|
|
|
| |
the length of happens to be larger than MAXPATHLEN.
PR: bin/74368
Submitted by: Max Okumoto <okumoto@ucsd.edu>
Obtained from: DragonFlyBSD
|
|
|
|
|
| |
Submitted by: Janusz Muc'ka (Defacto) <gdef at cvd dot pl>
MFC after: 3 days
|
|
|
|
|
| |
trigger for other misbehaviour in the sym driver that was causing freezes at
boot. Thanks to phk@ for reporting and testing this.
|
|
|
|
|
|
|
|
| |
2km away from where I'm living, so that I can fix these typos sooner.
s/SA_MAX/AF_MAX/ is previous commit.
Reported by: marcus, ups, Yiawei Ye, dwhite
|
|
|
|
|
|
| |
to the list functions for better readability.
Submitted by: Max Okumoto <okumoto@ucsd.edu>
|
|
|
|
|
|
| |
Remove reference to /dev/lomac, which is no longer used by mac_lomac(4).
MFC after: 3 days
|
| |
|
| |
|
| |
|