linux-kernel - Re: [PATCH] module: Enable dynamic debugging regardless of taint

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Nov 2011 15:11:10 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Jason Baron <jbaron@...hat.com>,
	Nick Bowler <nbowler@...iptictech.com>,
	Greg KH <greg@...ah.com>, Dave Jones <davej@...hat.com>,
	Randy Dunlap <rdunlap@...otime.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Debian kernel maintainers <debian-kernel@...ts.debian.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Subject: Re: [PATCH] module: Enable dynamic debugging regardless of taint

On Tue, 01 Nov 2011 03:59:33 +0000, Ben Hutchings <ben@...adent.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@...adent.org.uk>

Thanks, applied, unless Mathieu objects...

Cheers,
Rusty.
--
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/