From: Paul Mackerras <paulus@samba.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Sachin P. Sant" <sachinp@in.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
linuxppc-dev@ozlabs.org, linux-ext4@vger.kernel.org,
Jan Kara <jack@ucw.cz>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Crash (ext3 ) during 2.6.29-rc6 boot
Date: Mon, 23 Feb 2009 21:32:47 +1100 [thread overview]
Message-ID: <18850.31567.212454.514549@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20090223021320.11019d64.akpm@linux-foundation.org>
Andrew Morton writes:
> It looks like we died in ext3_xattr_block_get():
>
> memcpy(buffer, bh->b_data + le16_to_cpu(entry->e_value_offs),
> size);
>
> Perhaps entry->e_value_offs is no good. I wonder if the filesystem is
> corrupted and this snuck through the defenses.
>
> I also wonder if there is enough info in that trace for a ppc person to
> be able to determine whether the faulting address is in the source or
> destination of the memcpy() (please)?
It appears to have faulted on a load, implicating the source. The
address being referenced (0xc00000003f380000) doesn't look
outlandish. I wonder if this kernel has CONFIG_DEBUG_PAGEALLOC turned
on, and what page size is selected?
Paul.
next prev parent reply other threads:[~2009-02-23 10:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 9:46 Sachin P. Sant
2009-02-23 10:13 ` Andrew Morton
2009-02-23 10:32 ` Paul Mackerras [this message]
2009-02-23 10:57 ` Sachin P. Sant
2009-02-23 15:51 ` Jan Kara
2009-02-24 6:38 ` Sachin P. Sant
2009-02-24 15:51 ` Jan Kara
2009-02-25 1:20 ` Mark Nelson
2009-02-25 6:52 ` Mark Nelson
2009-02-25 9:50 ` Geert Uytterhoeven
2009-02-25 12:10 ` Mark Nelson
2009-02-25 13:31 ` Geert Uytterhoeven
2009-02-25 22:45 ` Mark Nelson
2009-02-25 23:20 ` Mark Nelson
2009-02-26 17:40 ` Geert Uytterhoeven
2009-02-25 11:08 ` Sachin P. Sant
2009-02-25 12:13 ` Mark Nelson
2009-02-25 23:26 ` [PATCH] powerpc: Fix 64bit memcpy() regression Mark Nelson
2009-02-25 23:46 ` [PATCH] powerpc: Fix 64bit __copy_tofrom_user() regression Mark Nelson
2009-02-24 18:01 ` Crash (ext3 ) during 2.6.29-rc6 boot Geert Uytterhoeven
2009-02-25 1:27 ` Mark Nelson
2009-02-25 10:50 ` Geert Uytterhoeven
2009-02-23 10:48 ` Sachin P. Sant
2009-02-24 16:14 ` Jan Kara
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=18850.31567.212454.514549@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@linux-foundation.org \
--cc=jack@ucw.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=sachinp@in.ibm.com \
/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®