lock violation in unionfs (9.0-STABLE r230270)
attilio at freebsd.org
Wed Aug 8 15:32:21 UTC 2012
On 8/8/12, Harald Schmalzbauer <h.schmalzbauer at omnilan.de> wrote:
> 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?:
>>> 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?
There are more things to fix in inode instantiation for unionfs. I
hope to make a comprehensive patch for tests in a couple of days.
Peace can only be achieved by understanding - A. Einstein
More information about the freebsd-stable