All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch@vger.kernel.org,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] initrd: Fix virtual/physical mix-up in overwrite test
Date: Sun, 15 Jun 2008 16:07:45 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806151606320.5736@anakin> (raw)
In-Reply-To: <Pine.LNX.4.64.0712231142190.24252@anakin>

On Sun, 23 Dec 2007, Geert Uytterhoeven wrote:
> New version below. Tested on Amiga. Compile-tested on ia32 (i386_defconfig) and
> pp64 (ps3_defconfig).

Ping?

> Subject: initrd: Fix virtual/physical mix-up in overwrite test
> 
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> 
> On recent kernels, I get the following error when using an initrd:
> 
> | initrd overwritten (0x00b78000 < 0x07668000) - disabling it.
> 
> My Amiga 4000 has 12 MiB of RAM at physical address 0x07400000 (virtual
> 0x00000000).
> The initrd is located at the end of RAM: 0x00b78000 - 0x00c00000 (virtual).
> The overwrite test compares the (virtual) initrd location to the (physical)
> first available memory location, which fails.
> 
> This patch converts initrd_start to a page frame number, so it can be safely
> compared with min_low_pfn.
> 
> Before the introduction of discontiguous memory support on m68k
> (12d810c1b8c2b913d48e629e2b5c01d105029839), min_low_pfn was just left
> untouched by the m68k-specific code (zero, I guess), and everything worked
> fine.
> 
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> On several platforms, initrd_below_start_ok is set to 1:
> 
> | arch/mips/kernel/setup.c:       initrd_below_start_ok = 1;
> | arch/parisc/mm/init.c:                  initrd_below_start_ok = 1;
> | arch/powerpc/kernel/prom.c:                     initrd_below_start_ok = 1;
> | arch/ppc/platforms/hdpu.c:                      initrd_below_start_ok = 1;
> | arch/xtensa/kernel/setup.c:             initrd_below_start_ok = 1;
> 
> Some of these may be workarounds for this bug. Please check.
> 
>  init/main.c |    5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> --- a/init/main.c
> +++ b/init/main.c
> @@ -598,9 +598,10 @@ asmlinkage void __init start_kernel(void
>  
>  #ifdef CONFIG_BLK_DEV_INITRD
>  	if (initrd_start && !initrd_below_start_ok &&
> -			initrd_start < min_low_pfn << PAGE_SHIFT) {
> +	    page_to_pfn(virt_to_page(initrd_start)) < min_low_pfn) {
>  		printk(KERN_CRIT "initrd overwritten (0x%08lx < 0x%08lx) - "
> -		    "disabling it.\n",initrd_start,min_low_pfn << PAGE_SHIFT);
> +		    "disabling it.\n",
> +		    page_to_pfn(virt_to_page(initrd_start)), min_low_pfn);
>  		initrd_start = 0;
>  	}
>  #endif

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-06-15 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 10:51 [PATCH] initrd: Fix virtual/physical mix-up in overwrite test Geert Uytterhoeven
2007-12-17  4:14 ` Roman Zippel
2007-12-18 11:01 ` Andrew Morton
2007-12-18 19:52   ` Geert Uytterhoeven
2007-12-18 20:31     ` Andrew Morton
2007-12-23 10:43       ` Geert Uytterhoeven
2008-06-15 14:07         ` Geert Uytterhoeven [this message]
2008-06-16  1:11           ` Andrew Morton
2008-06-16  6:20             ` Geert Uytterhoeven
2008-06-16  7:04               ` Geert Uytterhoeven

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=Pine.LNX.4.64.0806151606320.5736@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.