Date: Sat, 8 Sep 2007 07:02:33 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Maxim Sobolev <sobomax@freebsd.org> Cc: stable@freebsd.org Subject: Re: kqueue LOR Message-ID: <20070908040233.GP53667@deviant.kiev.zoral.com.ua> In-Reply-To: <46E19D4E.1060009@FreeBSD.org> References: <46E19D4E.1060009@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--JaBjgNvtdKe5H086 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 07, 2007 at 11:49:50AM -0700, Maxim Sobolev wrote: > Hi, >=20 > On my 6.2 system I am seeing LOR discussed almost 1 year ago here: >=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/031048.ht= ml > http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031197.ht= ml >=20 > lock order reversal: > 1st 0xc52cb500 kqueue (kqueue) @ kern/kern_event.c:1547 > 2nd 0xc4e4d80c struct mount mtx (struct mount mtx) @=20 > ufs/ufs/ufs_vnops.c:138 >=20 > Do you have any plans to commit the suggested fix? I suspect that the LOR is bogus. I was never able to get the information where the reverse lock order happen. What I asked of the most reporters is to apply sys/kern/subr_witness.c rev. 1.222 to RELENG_6 and provide me with the LOR report, if any. Note that doing that on RELENG_6_2 makes no sense, most likely you will get LORs with cdev mutex, fixed in RELENG_6. --JaBjgNvtdKe5H086 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG4h7ZC3+MBN1Mb4gRAhmwAKDk59Mk3TGgT1iDtHEzTPE1jgWeNQCfUTHP xZz7xBrzC7xNSSuExyWvVSs= =jJaO -----END PGP SIGNATURE----- --JaBjgNvtdKe5H086--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070908040233.GP53667>