2010/12/7 Erik Cederstrand <erik@cederstrand.dk>:
quoted text
>
> 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:
>>
>>> A Dmesg.TXT is attached having a lock order reversal .
>>
>>    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?

Witness has an 'internal blessing list' we never wanted to use in
order to keep them popping up as reminder.
Actually, the fact the LOR is 'known' doesn't mean it is 'analyzed'.
The very few 'Analyzed but harmless' cases in the past have been
handled via _NOWITNESS flags I guess.

Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"