linux-kernel - Re: [PATCH] Solve the issue with memory corruption on Intel BIOS.

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, 15 Jul 2009 10:34:31 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Alexey Fisher <bug-track@...her-privat.net>
Cc:	ykzhao <yakui.zhao@...el.com>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, mingo@...e.hu,
	Alexey Fisher <bug-track@...her-privat.net>
Subject: Re: [PATCH] Solve the issue with memory corruption on Intel BIOS.

On Wed, 15 Jul 2009 07:55:14 +0200
Alexey Fisher <bug-track@...her-privat.net> wrote:

> In Bug 13710 was reported "corrupted low memory after resume on Intel
> DG45ID board". It use AMI BIOS with Intel vendor string. We need to add this
> vendor to CONFIG_X86_RESERVE_LOW_64K workaround.

Given that this is the first report of a problem with an Intel BIOS, and
there are millions of systems not affected your match is far too wide I
think. Match the board identifier as well at least rather than randomly
making everyone suffer.

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