From: David Woodhouse <dwmw2@infradead.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linuxppc-dev@ozlabs.org, torvalds@linux-foundation.org,
john stultz <johnstul@us.ibm.com>
Subject: Re: Make sure we populate the initroot filesystem late enough
Date: Sun, 25 Feb 2007 19:00:57 -0500 [thread overview]
Message-ID: <1172448057.3971.9.camel@shinybook.infradead.org> (raw)
In-Reply-To: <200612112059.kBBKx1j7022473@hera.kernel.org>
On Mon, 2006-12-11 at 20:59 +0000, Linux Kernel Mailing List wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d610dd52dd1da696e199e4b4545f33a2a5de5c6
> Commit: 8d610dd52dd1da696e199e4b4545f33a2a5de5c6
> Parent: 8993780a6e44fb4e7ed34e33458506a775356c6e
> Author: Linus Torvalds <torvalds@woody.osdl.org>
> AuthorDate: Mon Dec 11 12:12:04 2006 -0800
> Committer: Linus Torvalds <torvalds@woody.osdl.org>
> CommitDate: Mon Dec 11 12:12:04 2006 -0800
>
> Make sure we populate the initroot filesystem late enough
>
> We should not initialize rootfs before all the core initializers have
> run. So do it as a separate stage just before starting the regular
> driver initializers.
>
> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This seems to be what's triggering the apparent memory corruption we've
been seeing recently -- in the case of the Fedora kernel it manifests
itself as a BUG() in cache_alloc_refill() when the pmac ide driver
initialises.
Another report was at http://lkml.org/lkml/2006/12/17/4
We've been seeing it on a Mac Mini too, and I managed to reproduce it on
my shinybook this evening by booting with 'mem=512M'.
One side-effect of this patch is to move the call to free_initrd() much
later in the init sequence, potentially after other memory management
code is assuming it's already been freed.
--
dwmw2
next parent reply other threads:[~2007-02-26 0:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612112059.kBBKx1j7022473@hera.kernel.org>
2007-02-26 0:00 ` David Woodhouse [this message]
2007-02-26 0:24 ` Make sure we populate the initroot filesystem late enough Linus Torvalds
2007-02-26 0:45 ` David Woodhouse
2007-02-26 1:17 ` David Woodhouse
2007-02-26 3:45 ` Linus Torvalds
2007-02-26 4:01 ` David Woodhouse
2007-02-26 4:13 ` Linus Torvalds
2007-02-26 16:24 ` David Woodhouse
2007-02-26 6:59 ` William Lee Irwin III
2007-02-26 15:53 ` Benjamin Herrenschmidt
2007-02-26 16:00 ` Segher Boessenkool
2007-02-26 16:44 ` Milton Miller
2007-02-26 20:57 ` David Woodhouse
2007-02-26 21:17 ` Linus Torvalds
2007-02-27 6:46 ` Benjamin Herrenschmidt
2007-02-26 15:51 ` Benjamin Herrenschmidt
2007-02-26 20:51 ` Kumar Gala
2007-02-26 19:27 ` john stultz
2007-02-26 22:27 ` Paul TBBle Hampson
2007-02-27 6:48 ` Benjamin Herrenschmidt
2007-02-27 11:58 ` Segher Boessenkool
2007-02-28 6:43 ` Benjamin Herrenschmidt
2007-02-28 10:13 ` David Woodhouse
2007-03-01 0:30 ` Michael Ellerman
2007-03-12 23:01 ` Paul TBBle Hampson
2007-03-13 3:03 ` Kumar Gala
2007-03-13 7:03 ` Benjamin Herrenschmidt
2007-03-16 7:20 ` Paul TBBle Hampson
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=1172448057.3971.9.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).