public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nick Bowler <nbowler@elliptictech.com>,
	mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	a.p.zijlstra@chello.nl, tglx@linutronix.de, mingo@elte.hu,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/locking] lockdep, bug: Exclude TAINT_FIRMWARE_WORKAROUND from disabling lockdep
Date: Tue, 06 Dec 2011 15:43:35 +0000	[thread overview]
Message-ID: <1323186215.7454.271.camel@deadeye> (raw)
In-Reply-To: <20111206154206.441e85c6@lxorguk.ukuu.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]

On Tue, 2011-12-06 at 15:42 +0000, Alan Cox wrote:
> On Tue, 6 Dec 2011 10:13:45 -0500
> Nick Bowler <nbowler@elliptictech.com> wrote:
> 
> > On 2011-12-06 01:38 -0800, tip-bot for Peter Zijlstra wrote:
> > > Commit-ID:  df754e6af2f237a6c020c0daff55a1a609338e31
> > > Gitweb:     http://git.kernel.org/tip/df754e6af2f237a6c020c0daff55a1a609338e31
> > > Author:     Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > AuthorDate: Mon, 14 Nov 2011 13:13:49 +0100
> > > Committer:  Ingo Molnar <mingo@elte.hu>
> > > CommitDate: Tue, 6 Dec 2011 08:16:47 +0100
> > > 
> > > lockdep, bug: Exclude TAINT_FIRMWARE_WORKAROUND from disabling lockdep
> > > 
> > > It's unlikely that TAINT_FIRMWARE_WORKAROUND causes false
> > > lockdep messages, so do not disable lockdep in that case.
> > > We still want to keep lockdep disabled in the
> > > TAINT_OOT_MODULE case:
> > > 
> > >   - bin-only modules can cause various instabilities in
> > >     their and in unrelated kernel code
> > > 
> > >   - they are impossible to debug for kernel developers
> > > 
> > >   - they also typically do not have the copyright license
> > >     permission to link to the GPL-ed lockdep code.
> > 
> > This is all bogus.  We have a proprietary module taint for the above.
> > Out of tree does not mean "bin-only", "non-GPL" or anything else like
> > that.  
> 
> It also stops people developing drivers of their own who are not
> building them in the kernel tree currently (eg when I'm building tests
> of the GMA500 graphics driver). This is a ludicrous patch and should be
> reverted

My change to set TAINT_OOT_MODULE had the (unintentional) effect of
disabling lockdep for OOT modules.  I subsequently proposed to change
that (while adding taint flags to lockdep output).  This patch doesn't
make any change either way.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-12-06 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  9:38 [tip:core/locking] lockdep, bug: Exclude TAINT_FIRMWARE_WORKAROUND from disabling lockdep tip-bot for Peter Zijlstra
2011-12-06 15:13 ` Nick Bowler
2011-12-06 15:30   ` Ben Hutchings
2011-12-06 15:42   ` Alan Cox
2011-12-06 15:43     ` Ben Hutchings [this message]
2011-12-06 17:43     ` Ingo Molnar
2011-12-06 17:52       ` Alan Cox
2011-12-06 18:13         ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1323186215.7454.271.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=nbowler@elliptictech.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox