Date: Wed, 08 Aug 2012 17:21:47 +0200 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: Pavel Polyakov <bsd@kobyla.org> Cc: Attilio Rao <attilio@freebsd.org>, stable@freebsd.org, daichi@freebsd.org Subject: Re: lock violation in unionfs (9.0-STABLE r230270) Message-ID: <5022840B.3060708@omnilan.de> In-Reply-To: <op.waqux6rr9gyv16@cel.home> References: <op.v9l1byf89gyv16@pp> <CAJ-FndAFMV2iHcMKvMruCP%2BHRzwQuY1Jcd_o6ZEnTCiPV8_8oA@mail.gmail.com> <op.waqux6rr9gyv16@cel.home>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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? Thanks, -Harry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlAihAsACgkQLDqVQ9VXb8hwvACgh6kDoDttxuSAu+sc+D/C7u3W bLoAoMHA5viZpJHwFmXISKt7FCsxsp+T =NnpT -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5022840B.3060708>