Date: Tue, 7 Dec 2010 10:57:36 +0100 From: Erik Cederstrand <erik@cederstrand.dk> To: Garrett Cooper <yanegomi@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Lock order reversal . Message-ID: <E00F6925-CEFD-465F-925F-5614210166CC@cederstrand.dk> In-Reply-To: <44B787D8-243C-4880-A532-261435C89940@gmail.com> References: <AANLkTin3njw-_4HRDw2en68LYhPC_XBDtXZp9U8gr3az@mail.gmail.com> <44B787D8-243C-4880-A532-261435C89940@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-18--123955561 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Den 07/12/2010 kl. 10.20 skrev Garrett Cooper: > On Dec 7, 2010, at 12:26 AM, Mehmet Erol Sanliturk = <m.e.sanliturk@gmail.com> wrote: >=20 >> A Dmesg.TXT is attached having a lock order reversal . >=20 > The mount LOR is well known. I see that this is the standard response to lot's of LOR reports. It = seems to be one of the most-reported errors on CURRENT (and it's = certainly a loud one), but I think a lot of people waste time = researching the error and browsing Bjoerns LOR page, only to get the = above response (not picking on you, Garrett). Do we have the possibility of silencing well-known and presumably = harmless LOR's if there isn't sufficient motivation to fix the source? Erik= --Apple-Mail-18--123955561--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E00F6925-CEFD-465F-925F-5614210166CC>