linux-kernel - Re: [bug] PCI hotplug, ibmphp_access_ebda: WARNING: at arch/x86/mm/ioremap.c:182 __ioremap

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080731112928.GC24030@elte.hu>
Date:	Thu, 31 Jul 2008 13:29:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	linux-kernel@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Yinghai Lu <yhlu.kernel@...il.com>, greg@...ah.com
Subject: Re: [bug] PCI hotplug, ibmphp_access_ebda: WARNING: at
	arch/x86/mm/ioremap.c:182 __ioremap_caller+0x2d1/0x340()


* Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> On Saturday, July 26, 2008 6:15 am Ingo Molnar wrote:
> > FYI, -tip testing triggered the new warning below on a testbox. I
> > suspect it's related to recent commits in drivers/pci/hotplug/.
> > I'm wondering, why does a driver map the EBDA? That's a really lowlevel
> > thing.
> 
> AFAICT, this driver digs around in there for hotplug controller 
> configuration (cc'ing Greg since he appears to be one of the original 
> authors).  It's a custom platform driver too, that may be the only 
> method available there.  Is there a shadow copy of the EDBA somewhere 
> we should be using instead?

not that i know of, but it could be provided i guess. Enumerating and 
making all hw configuration data available reliably would be a plus i 
guess.

	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/