On 8/8/12, Harald Schmalzbauer <h.schmalzba...@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 >>> >>> Pavel, >>> 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. >> >> Thanks! >> This patch fixes the problem with lock violation. Sorry I've tested it so >> late. > > Hello, > > 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. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
