| Age | Commit message (Collapse) | Author |
|---|
|
from freebsd text
|
|
|
|
cardbus_conf_read/cardbus_conf_write. This makes fxp* at cardbus?
work (again?) on macppc. tested by various users.
|
|
Thanks for krw@ for testing isa floppies. brad@ ok,
jason@ ok.
|
|
|
|
ok krw@
|
|
function as this is already done in the MII tick handler just before calling
the autonegotiation function.
ok krw@
|
|
|
|
naddy@, ok naddy@.
|
|
files under some special circumstances. remove a bogus stat() check to
fix it.
ok joris@
|
|
- when checking for the parity error itself:
+ use pmap_kenter_pa() and pmap_kremove() for the temporary mapping.
+ reenable external cache before invoking pmap_kremove() [which can cause
a cache flush on some models].
|
|
|
|
this is better than panic'ing due to low memory condition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This means that for now a config file can build us3 kernels
ok jason
|
|
|
|
found by mk, ok deraadt
|
|
|
|
|
|
After a rmdir()ed directory has been truncated, force an update of
the directory's inode after queuing the dirrem that will decrement
the parent directory's link count. This will force the update of
the parent directory's actual link to actually be scheduled. Without
this change the parent directory's actual link count would not be
updated until ufs_inactive() cleared the inode of the newly removed
directory, which might be deferred indefinitely. ufs_inactive()
will not be called as long as any process holds a reference to the
removed directory, and ufs_inactive() will not clear the inode if
the link count is non-zero, which could be the result of an earlier
system crash.
If a background fsck is run before the update of the parent directory's
actual link count has been performed, or at least scheduled by
putting the dirrem on the leaf directory's inodedep id_bufwait list,
fsck will corrupt the file system by decrementing the parent
directory's effective link count, which was previously correct
because it already took the removal of the leaf directory into
account, and setting the actual link count to the same value as the
effective link count after the dangling, removed, leaf directory
has been removed. This happens because fsck acts based on the
actual link count, which will be too high when fsck creates the
file system snapshot that it references.
This change has the fortunate side effect of more quickly cleaning
up the large number dirrem structures that linger for an extended
time after the removal of a large directory tree. It also fixes a
potential problem with the shutdown of the syncer thread timing out
if the system is rebooted immediately after removing a large directory
tree.
|
|
|
|
problem reported by will h. backman;
sorted with the author's permission - thanks henry spencer.
|
|
- add: creates <name>,t file with initial description if -m option was used.
- commit: uses <name>,t content (if it exists) to set the file description
OK joris@.
|
|
ok deraadt
|
|
overcompensating. From DragonFly, uses recent adjtime(2) changes,
so you'll need a recent kernel. ok henning@
|
|
|
|
'openssl x509 -hash'. ok beck@
|
|
|
|
'openssl x509 -hash'. ok beck@
|
|
|
|
|
|
|
|
|
|
spotted by deraadt@
|
|
- set traffic class (in PCI config space) to 0
- clean up the interrupt handler
- always read/write the INTCTL register with 4 bytes
- before resetting, ensure RUN bit is zero
- zero the BDP regs during reset
- still has a bunch of hacks in it to get it working, but at least
it interrupts correctly on my workstation now.
|
|
|
|
dispells some magic numbers
|
|
|
|
|
|
|
|
TLB-friendly cache function. From NetBSD.
|
|
'route show' dump out repeated copies of the v6 routing table on ramdisks.
on some architectures it spins forever doing this, on others it just
goes for a long time printing the v6 routes over and over before terminating.
spotted by jmc and krw, backout diff tested by beck.
|
|
here, make sure they compile with or without IPSEC, you morons!
|
