public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Rusty Russell <rusty@rustcorp.com.au>, Jason Baron <jbaron@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>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: Re: [PATCH 2/2] module: Re-enable dynamic debugging for GPL-compatible OOT modules
Date: Mon, 31 Oct 2011 13:44:17 +0000	[thread overview]
Message-ID: <1320068657.6759.107.camel@deadeye> (raw)
In-Reply-To: <87obwxq5tz.fsf@rustcorp.com.au>

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

On Mon, 2011-10-31 at 12:29 +1030, Rusty Russell wrote:
> On Fri, 28 Oct 2011 04:38:14 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> > Dynamic debugging was enabled for GPL-compatible out-of-tree modules
> > until my addition of TAINT_OOT_MODULE.  It should continue to be
> > enabled now.
> 
> Please just remove the test entirely.
> 
> AFAICT there's nothing unique to dynamic debug which means it should
> avoid taint.  If it oopses, we'll learn all about tainting in the oops
> message.

It looks like the dynamic debug facility is not meant to be available to
proprietary modules.

Ben.

> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > ---
> >  kernel/module.c |    4 ++--
> >  1 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/kernel/module.c b/kernel/module.c
> > index dab585e..448fd77 100644
> > --- a/kernel/module.c
> > +++ b/kernel/module.c
> > @@ -2881,7 +2881,7 @@ static struct module *load_module(void __user *umod,
> >  	}
> >  
> >  	/* This has to be done once we're sure module name is unique. */
> > -	if (!mod->taints || mod->taints == (1U<<TAINT_CRAP))
> > +	if (!(mod->taints & ~(1U << TAINT_CRAP | 1U << TAINT_OOT_MODULE)))
> >  		dynamic_debug_setup(info.debug, info.num_debug);
> >  
> >  	/* Find duplicate symbols */
> > @@ -2918,7 +2918,7 @@ static struct module *load_module(void __user *umod,
> >  	module_bug_cleanup(mod);
> >  
> >   ddebug:
> > -	if (!mod->taints || mod->taints == (1U<<TAINT_CRAP))
> > +	if (!(mod->taints & ~(1U << TAINT_CRAP | 1U << TAINT_OOT_MODULE)))
> >  		dynamic_debug_remove(info.debug);
> >   unlock:
> >  	mutex_unlock(&module_mutex);
> > -- 
> > 1.7.7
> > 
> > 
> 

-- 
Ben Hutchings
Computers are not intelligent.	They only think they are.

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

  reply	other threads:[~2011-10-31 13:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  3:38 [PATCH 2/2] module: Re-enable dynamic debugging for GPL-compatible OOT modules Ben Hutchings
2011-10-31  1:59 ` Rusty Russell
2011-10-31 13:44   ` Ben Hutchings [this message]
2011-11-01  2:09     ` Rusty Russell
2011-11-01  3:59       ` [PATCH] module: Enable dynamic debugging regardless of taint Ben Hutchings
2011-11-01  4:41         ` Rusty Russell
2011-11-01 12:48           ` Mathieu Desnoyers

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=1320068657.6759.107.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=davej@redhat.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=greg@kroah.com \
    --cc=jbaron@redhat.com \
    --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