linux-kernel - Re: [PATCH] x86: split e820 reserved entries record to late v4

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]

Date:	Sat, 6 Sep 2008 19:55:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: split e820 reserved entries record to late v4


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Fri, 29 Aug 2008, Ingo Molnar wrote:
> > 
> >  BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
> >  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> >  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> > 
> > which overlaps with the chipset PCI BAR (hpet) resource:
> > 
> >    pci 0000:00:14.0: BAR has HPET at fed00000-fed003ff
> > 
> > so due to this 1K conflict we take the full e820-reserved entry out and 
> > give the range 0xfec00000-0x100000000 as 'free'.
> 
> That's wrong. It's a full overlap, so "insert_resource()" should 
> happily insert the 00000000fec00000 - 0000000100000000 _around_ the 
> HPET bar.
> 
> Do you actually see this behavior, or do you just misunderstand how 
> "insert_resource()" works?

the latter, i misunderstood how it works.

	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/