hink using both may be causing problems.
KERNEL_LOCK forces lfs_lock, but not all KERNEL_LOCK users check for
lfs_lock.
The one that does (lfs_cluster_aiodone), does it within KERNEL_LOCK,
not outside.
dholland-t...@netbsd.org (David Holland) writes:
>Is there any reason lfs is using a global (rather than per-volume)
>lock? ad@ seems to have introduced it but as usual there's little in
>the way of reasoning or explanation.
After changing lfs to use the new locking primitives it was utterly
Is there any reason lfs is using a global (rather than per-volume)
lock? ad@ seems to have introduced it but as usual there's little in
the way of reasoning or explanation.
--
David A. Holland
dholl...@netbsd.org
