on 10/03/2010 19:31 Pawel Jakub Dawidek said the following:
> This should be impossible. If we are that deep in zfsvfs_teardown(), it means
> that we hold the z_teardown_lock exclusively. And we do as 'show alllocks'
> output confirms. But if we are holding this lock exclusively we shouldn't be
> that deep in create code path, because we need hold this lock as reader.
> It isn't visible in 'show alllocks' output, because this lock is special
BTW, it seems that our 'stock' rwlock implements exactly the same thing as
rrwlock.c - recursive readers, etc.