From: Ben Hutchings <ben@decadent.org.uk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>, Greg KH <greg@kroah.com>,
Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: Re: [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree
Date: Tue, 25 Oct 2011 11:52:46 +0200 [thread overview]
Message-ID: <1319536366.11727.0.camel@deadeye> (raw)
In-Reply-To: <87k47tpvvm.fsf@rustcorp.com.au>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Tue, 2011-10-25 at 14:26 +1030, Rusty Russell wrote:
> On Mon, 24 Oct 2011 07:57:03 -0700, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On 10/24/11 06:12, Ben Hutchings wrote:
> > > Use of the GPL or a compatible licence doesn't necessarily make the code
> > > any good. We already consider staging modules to be suspect, and this
> > > should also be true for out-of-tree modules which may receive very
> > > little review.
> > >
> > > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > > ---
> > > Debian has been carrying this for the last few kernel versions. The
> > > recent thread '[RFC] virtualbox tainting.' and discussions at KS suggest
> > > that this might be more generally useful.
> > >
> > > Ben.
> > >
> > > include/linux/kernel.h | 1 +
> > > kernel/module.c | 5 +++++
> > > kernel/panic.c | 2 ++
> > > scripts/mod/modpost.c | 7 +++++++
> > > 4 files changed, 15 insertions(+), 0 deletions(-)
> >
> > Hi,
> >
> > Please add 'O' to Documentation/oops-tracing.txt.
Sorry, this is the second time I've missed that now...
> I did that, and applied the patch. See below.
[...]
Thanks to everyone.
Ben.
--
Ben Hutchings
DNRC Motto: I can please only one person per day.
Today is not your day. Tomorrow isn't looking good either.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-10-25 9:53 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 [this message]
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
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=1319536366.11727.0.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=debian-kernel@lists.debian.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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).