From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andres Salomon" <dilinger@queued.net>
Cc: "Jan Beulich" <jbeulich@novell.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: ioremap ram check fix
Date: Wed, 30 Apr 2008 18:04:23 +0200 [thread overview]
Message-ID: <19f34abd0804300904x7000cc6q8d717c3cd524ada4@mail.gmail.com> (raw)
In-Reply-To: <20080430113024.43aa3935@ephemeral>
On Wed, Apr 30, 2008 at 5:30 PM, Andres Salomon <dilinger@queued.net> wrote:
> Hi Ingo,
>
> bdd3cee2e4b7279457139058615ced6c2b41e7de (x86: ioremap(), extend check
> to all RAM pages) breaks OLPC's ioremap call. The ioremap that OLPC uses is:
>
> romsig = ioremap(0xffffffc0, 16);
>
> The commit that breaks it is basically:
>
> - for (pfn = phys_addr >> PAGE_SHIFT; pfn < max_pfn_mapped &&
> - (pfn << PAGE_SHIFT) < last_addr; pfn++) {
> + for (pfn = phys_addr >> PAGE_SHIFT;
> + (pfn << PAGE_SHIFT) < last_addr; pfn++) {
> +
>
> Previously, the 'pfn < max_pfn_mapped' check would've caused us to not
> enter the loop. Removing that check means we loop infinitely. The
> reason for that is because pfn is 0xfffff, and last_addr is 0xffffffcf.
> The remaining check that is used to exit the loop is not sufficient;
> when pfn<<PAGE_SHIFT is 0xfffff000, that is less than 0xffffffcf; when
> we increment pfn and it overflows (pfn == 0x100000), pfn<<PAGE_SHIFT
> ends up being 0. That, of course, is less than last_addr. In effect,
> pfn<<PAGE_SHIFT is never lower than last_addr.
>
> The simple fix for this is to limit the last_addr check to the PAGE_MASK;
> a patch is below.
>
>
>
>
> Signed-off-by: Andres Salomon <dilinger@debian.org>
> ---
> arch/x86/mm/ioremap.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index 804de18..fb960f5 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -149,7 +149,8 @@ static void __iomem *__ioremap_caller(resource_size_t phys_addr,
> * Don't allow anybody to remap normal RAM that we're using..
> */
> for (pfn = phys_addr >> PAGE_SHIFT;
> - (pfn << PAGE_SHIFT) < last_addr; pfn++) {
> + (pfn << PAGE_SHIFT) < (last_addr & PAGE_MASK);
> + pfn++) {
>
> int is_ram = page_is_ram(pfn);
>
This fixes two 150-second solid freezes during bootup on a P4 I have
as well. Acked!
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-04-30 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 15:30 Andres Salomon
2008-04-30 16:04 ` Vegard Nossum [this message]
2008-04-30 18:10 ` Ingo Molnar
2008-04-30 18:17 ` Andres Salomon
2008-04-30 18:36 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0804300904x7000cc6q8d717c3cd524ada4@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®