[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zkgoo09f.fsf@rustcorp.com.au>
Date:	Wed, 26 Oct 2011 14:46:44 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Dave Jones <davej@...hat.com>, Greg KH <greg@...ah.com>
Cc:	Nick Bowler <nbowler@...iptictech.com>,
	Ben Hutchings <ben@...adent.org.uk>,
	Randy Dunlap <rdunlap@...otime.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Debian kernel maintainers <debian-kernel@...ts.debian.org>,
	Roland Vossen <rvossen@...adcom.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Subject: Re: [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree
On Tue, 25 Oct 2011 16:17:24 -0400, Dave Jones <davej@...hat.com> wrote:
> commit 7816c45bf13255157c00fb8aca86cb64d825e878
> Author: Roland Vossen <rvossen@...adcom.com>
> Date:   Thu Apr 7 11:20:58 2011 +0200
> 
>     modules: Enabled dynamic debugging for staging modules
...
>     
>     Signed-off-by: Roland Vossen <rvossen@...adcom.com>
>     Acked-by: Jason Baron <jbaron@...hat.com>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
Greg, you know better.  This is why we have maintainers: I can't track
patches I don't see.  Grrr...
> If we want to support out of tree modules with this, should we just nuke the
> whole check, or do we still want to prevent certain types of tainted kernels
> from using this stuff ?
It goes back to the first implementation of kernel markers.  IIRC, it
was to prevent dynamic debug stuff from circumventing licensing, but
testing for *any* taint seems overbroad.  Mathieu?
Thanks,
Rusty.
PS.  Can't see how this related to lockdep either...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
