schrieb Pavel Polyakov am 06.03.2012 11:20 (localtime):
>>> mount -t unionfs -o noatime /usr /mnt
>>> insmntque: mp-safe fs and non-locked vp: 0xfffffe01d96704f0 is not
>>> exclusive locked but should be
>>> KDB: enter: lock violation
>> can you give a spin to this patch?:
>> http://www.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch >>
>> I think that the unlocking is due at that point as the vnode lock can
>> be switch later on.
>> Let me know what you think about it and what the test does.
> This patch fixes the problem with lock violation. Sorry I've tested it so
this patch still applies cleanly to RELENG_9_1. Was there another fix
for the issue or has it just not been PR-sent and thus forgotten?