linux-kernel - Re: [PATCH v2 1/7] taint: add TAINT_DEBUG for invasive debugging features

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] [day] [month] [year] [list]

Message-ID: <20141020203714.GO28966@wotan.suse.de>
Date:	Mon, 20 Oct 2014 22:37:14 +0200
From:	"Luis R. Rodriguez" <mcgrof@...e.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	gregkh@...uxfoundation.org, dmitry.torokhov@...il.com,
	tiwai@...e.de, tj@...nel.org, arjan@...ux.intel.com, teg@...m.no,
	rmilasan@...e.com, werner@...e.com, oleg@...hat.com, hare@...e.com,
	bpoirier@...e.de, santosh@...lsio.com, pmladek@...e.cz,
	dbueso@...e.com, linux-kernel@...r.kernel.org,
	Jani Nikula <jani.nikula@...el.com>
Subject: Re: [PATCH v2 1/7] taint: add TAINT_DEBUG for invasive debugging
	features

On Wed, Oct 15, 2014 at 04:05:06PM +1030, Rusty Russell wrote:
> "Luis R. Rodriguez" <mcgrof@...not-panic.com> writes:
> > From: "Luis R. Rodriguez" <mcgrof@...e.com>
> >
> > At times we may add module parameters or debugging / testing
> > kernel features, when enabled though we don't really want
> > to be spending time debugging them. Add a taint flag for
> > this to avoid spurious bug reports.
> 
> The recently introduced KERNEL_PARAM_FL_UNSAFE flag for module
> parameters does this explicitly.  It uses TAINT_USER, should it use
> this instead?

Absolutely, dropped my taint thing in favor of this, thanks.

 Luis
--
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/