linux-kernel - Re: [PATCH] MODSIGN: Add TAINT_NOKEY

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

Date:	Sun, 20 Jan 2013 19:19:39 -0500
From:	"Frank Ch. Eigler" <fche@...hat.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Dave Jones <davej@...hat.com>, Josh Boyer <jwboyer@...hat.com>,
	dhowells@...hat.com, linux-kernel@...r.kernel.org,
	peterz@...radead.org, mingo@...hat.com,
	Len Brown <lenb@...nel.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
	linux-acpi@...r.kernel.org
Subject: Re: [PATCH] MODSIGN: Add TAINT_NOKEY_MODULE

Hi -

> [...]
> -	add_taint(TAINT_DIE);
> +	add_taint(TAINT_DIE, LOCKDEP_NOW_UNRELIABLE);
> [...]

If "UNRELIABLE" a good way to describe it - not DANGEROUS or
COUNTERPRODUCTIVE or something, then maybe lockdep *can* produce
reasonable results following such a taint.  If the results are merely
suspect, could lockdep reports include the taint report, but otherwise
keep working?

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