linux-kernel - Re: [PATCH 2/4] panic: Allow taint flag for warnings to be changed from 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] [day] [month] [year] [list]

Message-ID: <1269429075.2500.5.camel@concordia>
Date:	Wed, 24 Mar 2010 22:11:15 +1100
From:	Michael Ellerman <michael@...erman.id.au>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-s390@...r.kernel.org, linux-parisc@...r.kernel.org,
	linux-sh@...r.kernel.org, linux-pci@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, linuxppc-dev@...abs.org,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH 2/4] panic: Allow taint flag for warnings to be changed
 from TAINT_WARN

On Sat, 2010-03-20 at 23:05 +0000, Ben Hutchings wrote:
> WARN() is used in some places to report firmware or hardware bugs that
> are then worked-around.  These bugs do not affect the stability of the
> kernel and should not set the usual TAINT_WARN flag.  To allow for
> this, add WARN_TAINT() and WARN_TAINT_ONCE() macros that take a taint
> flag as argument.
..
> The architecture-specific changes here are untested and need to be
> reviewed by architecture maintainers.

I'm not one of them, but this at least builds on powerpc FWIW.

cheers

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)