From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Probe initrd header only if explicitly specified
Date: Tue, 26 Aug 2008 22:29:07 +0100 [thread overview]
Message-ID: <20080826212907.GB13647@linux-mips.org> (raw)
In-Reply-To: <20080826.223457.41872931.anemo@mba.ocn.ne.jp>
On Tue, Aug 26, 2008 at 10:34:57PM +0900, Atsushi Nemoto wrote:
> Currently init_initrd() probes initrd header at the last page of
> kernel image, but it is valid only if addinitrd was used. If
> addinitrd was not used, the area contains garbage so probing there
> might misdetect initrd header (magic number is not strictly robust).
>
> This patch introduces CONFIG_PROBE_INITRD_HEADER to enable this
> probing explicitly.
Applied though I think the solution isn't quite the most elegant ...
Ralf
next prev parent reply other threads:[~2008-08-26 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 13:34 [PATCH] Probe initrd header only if explicitly specified Atsushi Nemoto
2008-08-26 21:29 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 13:11 Atsushi Nemoto
2008-08-26 13:27 ` Geert Uytterhoeven
2008-08-26 13:31 ` Atsushi Nemoto
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=20080826212907.GB13647@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox