| 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
|
|
|
|
| |
No objections from: mlaier
|
|
|
|
|
|
|
|
|
|
| |
---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
|
|
|
|
| |
Submitted by: Leonardo Chiquitto Filho
|
|
|
|
|
|
|
|
| |
of $NANO_SRC, which can e.g. be used if the nanobsd scripts are not in
the source tree being built.
Improved by: phk
Approved by: phk
|
| |
|
|
|
|
|
|
| |
PR: 86522
Submitted by: Stephen Hurd <shurd@sasktel.net>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Don't reinitialise the atfork() handler list in the child. We
are meant to call the child handler, and on subsequent fork()s
should call all three functions as normal.
o Don't reinitialise the thread specific keyed data in the
child after a fork. Applications may require this for context.
o Reinitialise curthread->tlflags after removing ourselves from
(and reinitialising) the various internal thread lists.
o Reinitialise __malloc_lock in the child after fork() (to balance
our explicitly taking the lock prior to the fork()).
With these changes, it is possible to enable the NOTYET code in
thr_kern.c to allow the use of non-async-safe functions after
fork()ing from a threaded program.
Reviewed by: Daniel Eischen <deischen@freebsd.org>
[_malloc_lock reinitialisation has since been moved to avoid polluting the
!NOTYET code]
|
| |
|
|
|
|
|
|
|
|
| |
module is loaded or compiled into the kernel.
This is useful mostly in startup scripts, when module should be loaded only
if it wasn't compiled into the kernel nor already loaded, eg.:
kldstat -q -m g_eli || kldload geom_eli.ko || err 1 'geom_eli module failed to load.'
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
file either. This clears the way for third-party SSH ports to install
an RCng startup script.
|
|
|
|
| |
Approved by: pav (mentor)
|
|
|
|
|
| |
PR: bin/86343
Submitted by: Matej Vela <vela@debian.org>
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
PR: conf/81926
Submitted by: Gavin Atkinson <gavin.atkinson at ury dot york dot ac dot uk>
|
|
|
|
|
| |
PR: conf/82051
Submitted by: Derek Jones <derek at wahila dot com>
|
|
|
|
|
| |
PR: conf/86193
Submitted by: Matthias Buelow <mkb at incubus dot de>
|
| |
|
|
|
|
|
| |
the right thing by merging in the changes I neglected to commit last
night.
|
| |
|
|
|
|
|
|
| |
ports builds in the cluster to work correctly.
Tested by: kris
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
(not in mdoc(7) sense yet) in ifconfig(8) manpage, create such
subsections for gif(4) and vlan(4) so that their specific
options are not mixed up with general options.
|
|
|
|
|
|
| |
to 0x100000 in rev. 1.67.
- NOPT wasn't updated (decremented) in previous revision.
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
variable.
Tested by: Emil Mikulic
X-MFC-After: 6.0-RELEASE
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
"PC Card" is the correct spelling. "PC-Card" isn't, per the PCMCIA
standard.
|
|
|
|
|
|
|
|
| |
option was specified.
PR: bin/81231
Submitted by: "Daniel O'Connor" <doconnor@gsoft.com.au>
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
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.
|