Yes. And with my older (well, prehistoric ;) versions of the
drivers, "only" 20 or so of the tests resulted in a kernel panic
while the rest passed. So I'm hoping someone with more recent vfs
familiarity than myself can tell of the top of their head why a
namei on zfs results in this:
panic: kernel diagnostic assertion "VOP_ISLOCKED(*newsearchdir_ret)
== LK_EXCLUSIVE" failed
int
zfs_netbsd_lock(void *v)
{
struct vop_lock_args *ap = v;
return 0;
}
our port of ZFS doesn't obey the BSD locking rules. ZFS doesn't need
the BSD vnode lock for internal consistency since it does its own locking
internally, but the above check and possibly others have more recently
been added to ensure that file systems do the correct locking for the
fs-independent logic that relies on the BSD vnode lock.