linux-kernel - Re: Linux 2.6.31-rc4: strange change in iomem allocation

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]

Message-ID: <alpine.LFD.2.01.0907230926140.21520@localhost.localdomain>
Date:	Thu, 23 Jul 2009 09:29:13 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Frans Pop <elendil@...net.nl>
cc:	linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: Linux 2.6.31-rc4: strange change in iomem allocation



On Thu, 23 Jul 2009, Linus Torvalds wrote:
> 
> Don't worry about the new warning. 
> 
> It is in fact _normal_ to see a number of warnings about PnP resources 
> "could not be reserved"

In fact, I notice that you had them even before, eg:

	system 00:00: iomem range 0x0-0x9ffff could not be reserved
	system 00:00: iomem range 0xe0000-0xfffff could not be reserved
	system 00:00: iomem range 0x100000-0x7e7fffff could not be reserved

which are about exactly the same thing - e820 RAM reservations take 
precedence over the PnP ones.

So the only new thing is that we claim the APIC thing to that category 
too.

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