From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Saeed Bishara <saeed@marvell.com>,
Nicolas Pitre <nico@marvell.com>,
linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>
Subject: Re: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182)
Date: Fri, 14 May 2010 09:51:22 +1000 [thread overview]
Message-ID: <1273794682.21352.199.camel@pasglop> (raw)
In-Reply-To: <20100513151245.GA21251@quack.suse.cz>
On Thu, 2010-05-13 at 17:12 +0200, Jan Kara wrote:
> If you look at the array more in detail, you'll notice that 'offs' part of
> structure is sometimes identical. That should never happen because 'offs'
> contains offset of the corresponding directory entry in a block. So when
> offsets are identical in this array, subsequent move will copy some entries
> several times and leave entries that should be moved in the old block,
> resulting in a corruption we see.
> The question is, how could offsets be the same? dx_make_map seems to get
> it right and dx_sort_map as well. Maybe I'd peek into disassembly of
> dx_sort_map to see whether swap() macro does what it should... If that
> looks OK, you could try adding some debug checks into dx_sort_map and try
> to catch the moment when duplicate offsets are created...
Ok so a very quick test with another compiler and the problem -appears-
gone. I'll investigate more in depth later tonight or this week-end.
Looks like it may all have been a false alarm, just don't use
gcc-4.4.0 :-)
Cheers,
Ben.
prev parent reply other threads:[~2010-05-13 23:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 9:23 Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell 88f5182) Benjamin Herrenschmidt
2010-05-11 10:16 ` Jamie Lokier
2010-05-11 10:47 ` Benjamin Herrenschmidt
2010-05-11 10:57 ` Benjamin Herrenschmidt
2010-05-11 11:14 ` Shilimkar, Santosh
2010-05-12 22:21 ` Jamie Lokier
2010-05-12 22:47 ` Benjamin Herrenschmidt
2010-05-12 23:08 ` Russell King - ARM Linux
2010-05-14 17:41 ` Jamie Lokier
2010-05-14 17:59 ` Russell King - ARM Linux
2010-05-12 23:41 ` James Bottomley
2010-05-13 0:18 ` Benjamin Herrenschmidt
2010-05-13 15:39 ` James Bottomley
2010-05-13 23:53 ` Benjamin Herrenschmidt
2010-05-13 3:12 ` FUJITA Tomonori
2010-05-13 4:42 ` Benjamin Herrenschmidt
2010-05-12 15:00 ` Jan Kara
2010-05-12 22:13 ` Benjamin Herrenschmidt
2010-05-13 0:15 ` Benjamin Herrenschmidt
2010-05-13 15:12 ` Jan Kara
2010-05-13 21:33 ` Benjamin Herrenschmidt
2010-05-13 23:51 ` Benjamin Herrenschmidt [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=1273794682.21352.199.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jejb@parisc-linux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@marvell.com \
--cc=saeed@marvell.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;
as well as URLs for NNTP newsgroup(s).