Re: [PATCH 1/2] lockdep,rtmutex,bug: Show taint flags on error
- To: Ben Hutchings <ben@decadent.org.uk>, Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>
- Cc: Nick Bowler <nbowler@elliptictech.com>, Greg KH <greg@kroah.com>, Dave Jones <davej@redhat.com>, Randy Dunlap <rdunlap@xenotime.net>, LKML <linux-kernel@vger.kernel.org>, Debian kernel maintainers <debian-kernel@lists.debian.org>
- Subject: Re: [PATCH 1/2] lockdep,rtmutex,bug: Show taint flags on error
- From: Rusty Russell <rusty@rustcorp.com.au>
- Date: Mon, 31 Oct 2011 12:29:43 +1030
- Message-id: <[🔎] 87lis1q5tc.fsf@rustcorp.com.au>
- In-reply-to: <[🔎] 1319773015.6759.30.camel@deadeye>
- References: <[🔎] 1319773015.6759.30.camel@deadeye>
On Fri, 28 Oct 2011 04:36:55 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> Currently lock debugging is disabled when the kernel is tainted, with
> a few exceptions. It is already recognised that this can be useful
> for staging modules (TAINT_CRAP), but that also goes for out-of-tree
> modules (TAINT_OOT_MODULE) so long as core kernel developers don't
> have to spend time debugging them. Also, there are several reasons
> for tainting that are unlikely to introduce false locking bug reports
> (e.g. TAINT_FIRMWARE_WORKAROUND).
>
> Instead of disabling lock debugging, show the taint flags in all
> lockdep and rtmutex-debug error messages.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Reply to: