linux-kernel - Re: [PATCH v3] Add TAINT_HARDWARE

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:	Wed, 23 Jun 2010 16:00:48 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Matthew Garrett <mjg@...hat.com>
Cc:	Paul Mundt <lethal@...ux-sh.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Prarit Bhargava <prarit@...hat.com>,
	linux-kernel@...r.kernel.org,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: [PATCH v3] Add TAINT_HARDWARE_UNSUPPORTED flag

On Wed, Jun 23, 2010 at 04:30:47AM +0100, Matthew Garrett wrote:
> I don't think it's a flag that would ever be used in mainline, and 
> Alan's suggestion to just keep a range of taint flags as vendor-specific 
> would avoid the risk of collisions in future. But there's a minor 
> incentive to maintain standardisation over these things in order to 
> encourage commonality of report code.

Exactly.  This was why we posted this upstream to see if there were other
distros interested in a mechanism like this.

Cheers,
Don
--
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/