All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Jason Baron <jbaron@redhat.com>,
	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] module: Enable dynamic debugging regardless of taint
Date: Tue, 01 Nov 2011 15:11:10 +1030	[thread overview]
Message-ID: <87lis0v4ih.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1320119973.30281.7.camel@deadeye>

On Tue, 01 Nov 2011 03:59:33 +0000, Ben Hutchings <ben@decadent.org.uk> wrote:
> Dynamic debugging is currently disabled for tainted modules, except
> for TAINT_CRAP.  This prevents use of dynamic debugging for
> out-of-tree modules now that they are also tainted.
> 
> This condition was apparently intended to avoid a crash if a force-
> loaded module has an incompatible definition of dynamic debug
> structures.  However, a administrator that forces us to load a module
> is claiming that it *is* compatible even though it fails our version
> checks.  If they are mistaken, there are any number of ways the module
> could crash the system.
> 
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>

Thanks, applied, unless Mathieu objects...

Cheers,
Rusty.

  reply	other threads:[~2011-11-01  4: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
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 [this message]
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=87lis0v4ih.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=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 \
    /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.