msaitoh@ wrote:
(2014/02/15 1:58), Izumi Tsutsui wrote:
I'd suggest to clarify what problems you are trying to solve
and consider how it should be solved, before updating your patch.
The problems you mentioned are:
(1) merge initialization of sparse register mappings (with 4 byte
The current implementation of vn_lock() is racy. Modification of
the vnode oprations vector for active vnodes is unsafe because it
is not known whether deadfs or the original file system will be
called.
- Pass down LK_RETRY to the lock operation (hint for deadfs only).
- Split deadfs lock
On Fri, Feb 21, 2014 at 12:35:40PM +0100, J. Hannken-Illjes wrote:
The current implementation of vn_lock() is racy. Modification of
the vnode oprations vector for active vnodes is unsafe because it
is not known whether deadfs or the original file system will be
called.
- Pass down LK_RETRY
On Feb 21, 2014, at 1:06 PM, Thomas Klausner w...@netbsd.org wrote:
snip
I wanted to understand what you're describing here, but I don't know
what deadfs is, and apropos deadfs only pointed to hier(7). Could
someone please describe it, at best in a manpage? (I'm happy to help
with
