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  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]
Date:	Mon, 20 Oct 2014 22:37:14 +0200
From:	"Luis R. Rodriguez" <>
To:	Rusty Russell <>
Cc:	"Luis R. Rodriguez" <>,,,,,,,,,,,,,,,,
	Jani Nikula <>
Subject: Re: [PATCH v2 1/7] taint: add TAINT_DEBUG for invasive debugging

On Wed, Oct 15, 2014 at 04:05:06PM +1030, Rusty Russell wrote:
> "Luis R. Rodriguez" <> writes:
> > From: "Luis R. Rodriguez" <>
> >
> > 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists