linux-kernel - Re: resource map sanity check conflict

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, 8 Dec 2010 12:56:06 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	David Airlie <airlied@...ux.ie>,
	LKML <linux-kernel@...r.kernel.org>, abelay@....edu,
	Chris Wilson <chris@...is-wilson.co.uk>,
	Thomas Renninger <trenn@...e.de>
Subject: Re: resource map sanity check conflict

On Monday, December 06, 2010 01:34:56 pm Bjorn Helgaas wrote:
> On Monday, December 06, 2010 01:17:33 pm Jiri Slaby wrote:
> > On 11/24/2010 08:22 PM, Bjorn Helgaas wrote:
> > > On Wednesday, November 24, 2010 06:36:01 am Jiri Slaby wrote:
...
> > >> pnp 00:0a: [mem 0xfed40000-0xfed44fff]
> > >> pnp 00:0a: Plug and Play ACPI device, IDs ATM1200 PNP0c31 (active)
> > >> ...
> > >> resource map sanity check conflict: 0xfed40000 0xfed44fff 0xfed44000
...
> > > Yes, this is related to the PCI resource changes I made recently.
> > > We used to allocate PCI resources from low addresses first and work
> > > upwards, and now we do the reverse.  So in 2.6.36, the "Intel Flush
> > > Page" was probably allocated low in the [mem 0x7e000000-0xfebfffff]
> > > window, but now we put it in the [mem 0xfed40000-0xfed4bfff] window:
> > > 
> > >   pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff]
> > >   pci_root PNP0A08:00: host bridge window [mem 0xfed40000-0xfed4bfff]
> > > 
> > > I think the problem is that we ignore most of what ACPI tells us
> > > about motherboard device resource usage.  We do have the "system"
> > > driver, which reserves resources used by PNP0c01 and PNP0c02 devices,
> > > but we don't do anything about other devices like the ATM1200/PNP0c31
> > > device which, in your case, is using some of the space in that
> > > [mem 0xfed40000-0xfed4bfff] host bridge window.

> > I created the bko entry some time ago:
> > https://bugzilla.kernel.org/show_bug.cgi?id=23802

I have a patch here for testing:

  https://bugzilla.kernel.org/attachment.cgi?id=39262

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