All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
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, ben@decadent.org.uk,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/locking] lockdep, bug: Exclude TAINT_FIRMWARE_WORKAROUND from disabling lockdep
Date: Tue, 6 Dec 2011 19:13:18 +0100	[thread overview]
Message-ID: <20111206181318.GA9842@elte.hu> (raw)
In-Reply-To: <20111206175230.2c5b2ea0@lxorguk.ukuu.org.uk>


* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > My primary worry is to not have lockdep active when there's 
> > binary modules in a system - can TAINT_OOT_MODULE be set but 
> > TAINT_PROPRIETARY_MODULE not set for non-GPL modules?
> 
> Yes. I imagine anyone wanting to use lockdep with binary modules
> would just lie anyway.
> 
> > If not, and if TAINT_OOT_MODULE set and TAINT_PROPRIETARY_MODULE 
> > cleared guarantees the GPL-ness of the module then i have no 
> > problem with keeping lockdep active in that case.
> 
> Insofar as nobody is making their code line about licenses.

Fair enough - so i agree that we can allow OOT_MODULE's with 
lockdep and thus revert the lockdep-disabling effect of:

 2449b8ba0745: module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree

Thanks,

	Ingo

      reply	other threads:[~2011-12-06 18:15 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
2011-12-06 17:43     ` Ingo Molnar
2011-12-06 17:52       ` Alan Cox
2011-12-06 18:13         ` Ingo Molnar [this message]

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=20111206181318.GA9842@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ben@decadent.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.