All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: kuleshovmail@gmail.com, bp@suse.de, akpm@linux-foundation.org,
	bhe@redhat.com, dyoung@redhat.com, jroedel@suse.de,
	torvalds@linux-foundation.org, msalter@redhat.com,
	peterz@infradead.org, tglx@linutronix.de,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-next-20160302] Can't unpack initramfs.
Date: Sat, 5 Mar 2016 12:25:57 +0100	[thread overview]
Message-ID: <20160305112557.GC23473@gmail.com> (raw)
In-Reply-To: <201603051759.IFI12853.tFVHQLJOSFMOOF@I-love.SAKURA.ne.jp>


* Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:

> I'm hitting a problem that initramfs is corrupted when booting from GRUB2 on VMware Player 6.0.6.
> This problem does not occur when booting from qemu-kvm or from PXE on VMware Player 6.0.6.

> Bisection reached to "x86/setup: Calculate ramdisk parameters only once".

that commit is crap, as it changed the size calculation:

-       u64 ramdisk_size  = get_ramdisk_size();

-                     ramdisk_size);
+                     ramdisk->size);

+       struct ramdisk ramdisk = {
+              .start_addr      = get_ramdisk_image(),
+              .size            = PAGE_ALIGN(get_ramdisk_size()),
+              .reserve_ramdisk = true
+       };

I've zapped it.

Thanks,

	Ingo

      reply	other threads:[~2016-03-05 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 10:51 [linux-next-20160302] Can't unpack initramfs Tetsuo Handa
2016-03-05  8:59 ` Tetsuo Handa
2016-03-05 11:25   ` Ingo Molnar [this message]

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=20160305112557.GC23473@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bp@suse.de \
    --cc=dyoung@redhat.com \
    --cc=jroedel@suse.de \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msalter@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.