linux-kernel - Re: [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected))

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:	Sun, 13 Apr 2008 11:19:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Anvin" <hpa@...or.com>, Arjan van de Ven <arjan@...radead.org>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [rfc] hw resource debugging checks (was: Re: x86 git tree
	broken (bisected))


* Yinghai Lu <yhlu.kernel@...il.com> wrote:

> =====> just sent out one patch to work around that

yep, just applied that one.

> also BIOS is sick to allocate overlapping MMIO to the same link..
> 
> node 0 link 0: io port [1000, ffffff]
> TOM: 0000000080000000 aka 2048M
> node 0 link 0: mmio [e0000000, efffffff]
> node 0 link 0: mmio [a0000, bffff]
> node 0 link 0: mmio [80000000, ffffffff]
> bus: [00,ff] on node 0 link 0
> 
> never thought that BIOS could be so sick.
>  ===> already have one work around, need more test next week.

great!

basically any and all sickness should be assumed both by the hardware 
and by the BIOS, _and_ by Linux architecture code as well as it passes 
stuff to the generic driver layers. So as resources get set up we should 
have resilience all the way and should be on the lookout for signs of 
bugs - because breakages are so hard to track down in this area if they 
go unnoticed during setup.

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