linux-kernel - Re: 2.6.33-git6 boot failure[x86_64] (WARN: at arch/x86/mm/ioremap.c:111)

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.00.1003011728450.4245@localhost.localdomain>
Date:	Mon, 1 Mar 2010 17:31:00 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Wu Fengguang <fengguang.wu@...el.com>
cc:	Xiaotian Feng <xtfeng@...il.com>, Sachin Sant <sachinp@...ibm.com>,
	Yinghai Lu <yinghai@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	"x86@...nel.org" <x86@...nel.org>
Subject: Re: 2.6.33-git6 boot failure[x86_64] (WARN: at
 arch/x86/mm/ioremap.c:111)

On Mon, 1 Mar 2010, Wu Fengguang wrote:
 Ah walk_system_ram_range() is actually doing almost the same alignment
> check as the removed x86 page_is_ram(), except that it calls func()
> with len=0.  This happens when page_is_ram(cffa3000) is called.
> 
> walk_system_ram_range():
>     pfn = (unsigned long)(res.start >> PAGE_SHIFT);
>     len = (unsigned long)((res.end + 1 - res.start) >> PAGE_SHIFT);
>     ret = (*func)(pfn, len, arg);
> 
> The following patch should fix the problem.

Right, that should fix it. Though I wonder whether we should warn
prominently about non page aligned e820 mapping entries.

Thanks,

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