| Age | Commit message (Collapse) | Author |
|---|
|
are interested in software).
|
|
add a convention that if the driver returns ERESTART as an error
message of its process method, the crypto framework will unregister
the driver and migrate all its sessions. After discussion with Sam
Leffler and Jason Wright.
|
|
|
|
can call bus_dmamem_{map/unmap} safely, this is because this chip has
(you'll love this...) NO support for scatter-gather
- implement enough of the crypto(9) api to support the simple/stateless
operations: SHA1 and MD5 simple hash
- remove debugging EA queue handling
|
|
|
|
It's done automatically now.
|
|
interface except the given one. adjust the pf_test_* functions and
pf_skip_step accordingly.
ok dhartmei@
|
|
ok dhartmei@
|
|
non-executeable stack.
|
|
|
|
|
|
|
|
|
|
screwed entries
|
|
|
|
|
|
|
|
|
|
does not work
|
|
|
|
|
|
henric@attbi.com
|
|
|
|
|
|
pmap_t is the exception, it is required by the MI code so pmap_t will
be used instead of using 'struct pmap *' in the code. (consistency)
|
|
only i810 driver was tested though.
based on the netbsd's lkm, initially ported
by hunter@dg.net.ua and later made into shape by mickey.
testing by art@ and millert@ .
|
|
|
|
|
|
|
|
to get shared locks for lookup and get the exclusive lock only with
LK_DRAIN on unmount and do the real exclusive locking with flags in
mnt_flags, we now use shared locks for lookup and an exclusive lock for
unmount.
This is accomplished by slightly changing the semantics of vfs_busy.
Old vfs_busy behavior:
- with LK_NOWAIT set in flags, a shared lock was obtained if the
mountpoint wasn't being unmounted, otherwise we just returned an error.
- with no flags, a shared lock was obtained if the mountpoint was being
unmounted, otherwise we slept until the unmount was done and returned
an error.
LK_NOWAIT was used for sync(2) and some statistics code where it isn't really
critical that we get the correct results.
0 was used in fchdir and lookup where it's critical that we get the right
directory vnode for the filesystem root.
After this change vfs_busy keeps the same behavior for no flags and LK_NOWAIT.
But if some other flags are passed into it, they are passed directly
into lockmgr (actually LK_SLEEPFAIL is always added to those flags because
if we sleep for the lock, that means someone was holding the exclusive lock
and the exclusive lock is only held when the filesystem is being unmounted.
More changes:
dounmount must now be called with the exclusive lock held. (before this
the caller was supposed to hold the vfs_busy lock, but that wasn't always
true).
Zap some (now) unused mount flags.
And the highlight of this change:
Add some vfs_busy calls to match some vfs_unbusy calls, especially in
sys_mount. (lockmgr doesn't detect the case where we release a lock noone
holds (it will do that soon)).
If you've seen hangs on reboot with mfs this should solve it (I repeat this
for the fourth time now, but this time I spent two months fixing and
redesigning this and reading the code so this time I must have gotten
this right).
|
|
The flag can be either HOOK_REMOVE or HOOK_REMOVE|HOOK_FREE.
o HOOK_REMOVE removes the hook from the list before executing it.
o HOOK_FREE frees the hook after that.
- Let dostartuphooks use HOOK_REMOVE|HOOK_FREE so we can reclaim the memory.
- Let doshutdownhooks use HOOK_REMOVE so that when some shutdown hook
panics (they do that all the #@$%! time these days) we don't loop
for ever. Don't HOOK_FREE, it doesn't matter and I don't want to add
another possible panic condition for shutdown hooks.
- Actually free the pointer we're throwing away in hook_disestablish (I wonder
how much memory this has leaked over the years).
|
|
needed
|
|
|
|
|
|
|
|
has absolutely no use on wscons architectures.
|
|
|
|
Implemented with paranoia.
|
|
(shoulda caught this before like I caught const'fying it, oh well)
|
|
for fighting with 3com to make this happen!
|
|
firmware version.
|
|
|
|
|
|
From Lurene Angela Grenier <lurene@daemonkitty.net>
|
|
|
|
several days of debugging my laptop because underneath the X it was sitting
on the console waiting for me to press some key on the '--db_more--' prompt.
|
|
|
|
TODO: sort-of normalization against fragments for inspection
ok dhartmei@
|
|
|
|
|
