| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
need a sperate entry for it.
|
|
|
|
|
|
|
|
|
|
|
| |
slots to probe. Problems have been reported in this area, lets hope this
bandaid helps.
!! Owners of EISA-equipped Alpha machines are requested to at least
!! boot-test a 6-BETA build and report back to the Alpha list. Thanks!
Approved by: re (scottl)
Suggested by: ticso
|
|
|
|
|
|
|
|
|
|
| |
---snip---
FYI this bit isn't needed for FreeBSD - I think it came from either
OpenBSD or NetBSD where arc4random() wasn't available during cold
boot.
---snip---
Explained by: iedowse
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when we mount and get zero cost if no rules are used in a mountpoint.
Add code to deref rules on unmount.
Switch from SLIST to TAILQ.
Drop SYSINIT, use SX_SYSINIT and static initializer of TAILQ instead.
Drop goto, a break will do.
Reduce double pointers to single pointers.
Combine reaping and destroying rulesets.
Avoid memory leaks in a some error cases.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in rev. 1.40 of ufs_inode.c, which allows an inode being truncated
even when the filesystem itself is marked RDONLY. A subsequent
call of UFS_TRUNCATE (ffs_truncate) would panic the system as it
asserts that it can only be called when the filesystem is mounted
read-write (same changeset, rev. 1.74 of sys/ufs/ffs/ffs_inode.c).
Because ffs_mount() already takes care of sync'ing the filesystem
to disk before being downgraded to readonly, it appears to be more
desirable that we should not permit this sort of writes to disk.
This change would fix a panic that occours when read-only mounted
a corrupted filesystem and doing some file operations.
MT6/5/4 candidate
Reviewed by: mckusick
|
|
|
|
|
|
| |
before more recent holders.
MFC after: 3 days
|
|
|
|
|
|
|
| |
lock on the fifo vnode in fifo_open(): we rely on the vnode lock to
serialize access to v_fifoinfo.
MFC after: 3 days
|
| |
|
|
|
|
|
| |
the right thing by merging in the changes I neglected to commit last
night.
|
| |
|
|
|
|
|
|
| |
Tested by: kris@
Reviewed by: peter@
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
It confuses the lock manager since in some places thread0 is
then used for vnode locking while curthread is used for vnode unlocking.
Found by: Yahoo!
Reviewed by: ps@,jhb@
MFC after: 3 days
|
|
|
|
|
| |
boot_* variable. The end effect is that all flags from boot2
are now passed to the kernel.
|
|
|
|
| |
"boot_dfltroot", "boot_mute", and "boot_pause" respectively.
|
|
|
|
| |
are now gone from the tree.
|
|
|
|
|
|
| |
to 0x100000 in rev. 1.67.
- NOPT wasn't updated (decremented) in previous revision.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
underlying the POSIX fifo implementation. In 6.x/7.x, fifo access is
moved from the VFS layer, where it was serialized using the vnode
lock, to the file descriptor layer, where access is protected by a
reference count but not serialized. This exposed socket buffer
locking to high levels of parallelism in specific fifo workloads, such
as make -j 32, which expose as yet unresolved socket buffer bugs.
fi_sx re-adds serialization about the read and write routines,
although not paths that simply test socket buffer mbuf queue state,
such as the poll and kqueue methods. This restores the extra locking
cost previously present in some cases, but is an effective workaround
for the instability that has been experienced. This workaround should
be removed once the bug in socket buffer handling has been fixed.
Reported by: kris, jhb, Julien Gabel <jpeg at thilelli dot net>,
Peter Holm <peter at holm dot cc>, others
MFC after: 3 days
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
"PC Card" is the correct spelling. "PC-Card" isn't, per the PCMCIA
standard.
|
| |
|
|
|
|
|
|
| |
chips where setting the FAILDIS bit is not effective. While here,
try again to make it clear that reported parity errors indicate
a failure of some PCI device *other than* the aic7xxx controller.
|
| |
|
|
|
|
| |
avoid SCB ID collissions to non-packetized targets.
|
|
|
|
|
|
| |
timer reset rather than the timer of an SCB still pending on the
controller after recovery completed. This should correct timeout
loops seen in the field.
|
|
|
|
|
| |
is the default behavior according the the bootverbose printf in the
failure case.
|
| |
|
| |
|
|
|
|
|
|
|
| |
over from de__Ping.
# Didn't fix the -Exxxx return statements that appaer to be linuxisms
# (and wrong) since I don't have hardware to test with.
|
|
|
|
|
|
|
|
|
| |
copied mbuf, which keeps the IP header 32-bit aligned. This copied mbuf is
reinjected back into ether_input and off to the IP routines.
Reported and tested by: Peter van Dijk
Approved by: mlaier (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
a thread holding critical resource, e.g mutex or other implicit
synchronous flags. Give thread which exceeds nice threshold a minimum
time slice.
PR: kern/86087
|
| |
|
| |
|
|
|
|
| |
CIS are tiny, this likely hasn't bit anybody yet...
|
|
|
|
|
|
|
| |
namei() calls in kern_alternate_path().
Reviewed by: csjp
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
has been removed. It has been replaced by hw.pci.do_power_nodriver
and hw.pci.do_power_resume. The former defaults to 0 while the latter
defaults to 1.
When do_powerstate was set to 0, it broke suspend/resume for a lot of
people as an unintended consequence. This change will only affect the
areas that were intended to affect. This change will have no effect on
servers, but will help laptops quite a bit.
MFC After: 3 days.
|
|
|
|
|
|
|
| |
added it to GENERIC...
Pointed out by: jhb
Pointy hat: kensmith
|
|
|
|
|
|
|
|
| |
NULL. The NFS client expects that a thread will always be present for a
VOP so that it can check for signal conditions, and will dereference a
NULL pointer if one isn't present.
MFC after: 3 days
|
|
|
|
|
|
|
| |
I'm not sure this is the right thing to do, but at least I don't panic
anymore when swapping on a NFS file without using md(4).
X-MFC after: proper review
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Rearrange code so that in a case of failure the affected
route is not changed. Otherwise, a bogus rtentry will be
left and later rt_check() can recurse on its lock. [1]
- Remove comment about protocol cloning.
- Fix two places where rtentry mutex was recursed on, because
accessed via two different pointers, that were actually pointing
to the same rtentry in some cases. [1]
- Return EADDRINUSE instead of bogus EDQUOT, in case when gateway
uses the same route. [2]
Reported & tested by: ps, Andrej Zverev <az inec.ru> [1]
PR: kern/64090 [2]
|
|
|
|
|
|
|
|
| |
The FXP_SCR_FLOWCONTROL registers is at offset 0x19, but 2 bytes wide.
It cannot be read as a word without causing a panic on architectures
that enforce strict alignment.
MFC after: 3 days
|
|
|
|
|
|
|
| |
Don't destroy a NULL device.
This should fix the panics on boot people are seeing on systems with
more than one pccard slot.
|
| |
|
| |
|
| |
|
| |
|