From: Greg KH <greg@kroah.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Nick Bowler <nbowler@elliptictech.com>,
Dave Jones <davej@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>,
Randy Dunlap <rdunlap@xenotime.net>,
LKML <linux-kernel@vger.kernel.org>,
Debian kernel maintainers <debian-kernel@lists.debian.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: Re: [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree
Date: Thu, 27 Oct 2011 07:49:20 +0200 [thread overview]
Message-ID: <20111027054920.GA1388@kroah.com> (raw)
In-Reply-To: <874nyvnsqe.fsf@rustcorp.com.au>
On Thu, Oct 27, 2011 at 11:41:37AM +1030, Rusty Russell wrote:
> On Wed, 26 Oct 2011 09:08:34 -0400, Nick Bowler <nbowler@elliptictech.com> wrote:
> > On 2011-10-25 22:54 +0200, Greg KH wrote:
> > > On Tue, Oct 25, 2011 at 04:17:24PM -0400, Dave Jones wrote:
> > > > On Tue, Oct 25, 2011 at 10:04:55PM +0200, Greg Kroah-Hartman wrote:
> > > > > On Tue, Oct 25, 2011 at 12:51:42PM -0400, Nick Bowler wrote:
> > > > > > This is not the case: lockdep works fine with staging modules.
> > > > >
> > > > > Yes, that was fixed a few kernel versions ago.
> > > > >
> > > > > Now you might want to update that fix for the TAINT_OOT_MODULE flag as
> > > > > well, if you feel it is needed.
> > > >
> > > > I'm assuming you mean this patch ?
> > > >
> > > > commit 7816c45bf13255157c00fb8aca86cb64d825e878
> > > > Author: Roland Vossen <rvossen@broadcom.com>
> > > > Date: Thu Apr 7 11:20:58 2011 +0200
> > > >
> > > > modules: Enabled dynamic debugging for staging modules
> > >
> > > Hm, this is the patch I was thinking about yes. But as you point out:
> > [...]
> > > Perhaps the lockdep thing is totally different. I don't know about that
> > > check.
> >
> > Lockdep is disabled (for the whole system) by add_taint itself. The
> > relevant commit that fixes TAINT_CRAP appears to be this one (circa
> > 2.6.30):
> >
> > commit 574bbe782057fdf0490dc7dec906a2dc26363e20
> > Author: Frederic Weisbecker <fweisbec@gmail.com>
> > Date: Sat Apr 11 03:17:18 2009 +0200
> >
> > lockdep: continue lock debugging despite some taints
> >
> > I didn't know about the dynamic debug problem. Is there more breakage
> > that we haven't found yet? Remind me why we're trying to cripple out
> > of tree module users?
>
> Gah, people are overloading taint.
>
> It doesn't mean "don't do stuff", it means "note the taint when
> something goes wrong".
I agree, we shouldn't be changing logic in the kernel due to tainting,
so removing any such checks would be a good idea.
thanks,
greg k-h
next prev parent reply other threads:[~2011-10-27 6:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 13:12 [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree Ben Hutchings
2011-10-24 13:58 ` Dave Jones
2011-10-24 14:57 ` Randy Dunlap
2011-10-25 3:56 ` Rusty Russell
2011-10-25 9:52 ` Ben Hutchings
2011-10-25 15:38 ` Nick Bowler
2011-10-25 16:05 ` Ben Hutchings
2011-10-25 16:51 ` Nick Bowler
2011-10-25 20:04 ` Greg KH
2011-10-25 20:17 ` Dave Jones
2011-10-25 20:54 ` Greg KH
2011-10-26 13:08 ` Nick Bowler
2011-10-27 1:11 ` Rusty Russell
2011-10-27 1:55 ` Dave Jones
2011-10-31 1:30 ` Rusty Russell
2011-10-27 5:49 ` Greg KH [this message]
2011-10-26 4:16 ` Rusty Russell
2011-10-26 6:15 ` Mathieu Desnoyers
2011-10-25 1:37 ` Greg KH
2011-12-12 21:40 ` Luis R. Rodriguez
2011-12-12 21:58 ` Ben Hutchings
2011-12-12 22:47 ` Luis R. Rodriguez
2011-12-12 22:49 ` Luis R. Rodriguez
2011-12-13 5:02 ` Ben Hutchings
2011-12-14 16:20 ` [RFC] modpost: add option to allow external modules to avoid taint John W. Linville
2011-12-14 16:52 ` Ben Hutchings
2011-12-14 17:39 ` John W. Linville
[not found] ` <87mxatp3ty.fsf@rustcorp.com.au>
2011-12-16 4:39 ` Ben Hutchings
2011-12-19 5:45 ` Rusty Russell
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=20111027054920.GA1388@kroah.com \
--to=greg@kroah.com \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=nbowler@elliptictech.com \
--cc=rdunlap@xenotime.net \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).