From: Eric Sandeen <sandeen@sandeen.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: David Miller <davem@davemloft.net>,
byron.bbradley@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: XFS Fails Quality Assurance Tests on ARM
Date: Tue, 30 Oct 2007 00:47:35 -0500 [thread overview]
Message-ID: <4726C577.9000209@sandeen.net> (raw)
In-Reply-To: <p73ps12vxrl.fsf@bingen.suse.de>
Andi Kleen wrote:
> David Miller <davem@davemloft.net> writes:
>
>> From: Byron Bradley <byron.bbradley@gmail.com>
>> Date: Fri, 31 Aug 2007 03:12:46 +0000 (UTC)
>>
>>> Anybody got any ideas of how we fix this?
>> I don't know how much testing XFS gets on ARM, but one thing that some
>> ARM chips have is D-cache aliasing problems and one thing XFS uses a
>> lot is virtual remapping of various data structures via vmap().
>>
>> This might be what is causing the problems.
Sorry, I lost the original to reply to, but stumbled on this thread
looking for something else. :)
Anyway, from the assertion:
Assertion failed: (char *)sfep - (char *)sfp == dp->i_d.di_size, file:
fs/xfs/xfs_dir2_sf.c, line: 647 kernel BUG at fs/xfs/support/debug.c:82!
this is almost certainly a result of xfs_dir2_sf_off_t,
xfs_dir2_sf_hdr_t, and/or xfs_dir2_sf_entry_t or others not being
"properly" aligned on arm.
There was a patch floating around to "fix" it but it's not on-disk
compatible w/ x86 & friends, it just makes things consistent for arm. I
think packing some of these structures would take care of it, but this
problem could use some attention & testing I think, it's been floating
around a long time.
-Eric
next prev parent reply other threads:[~2007-10-30 5:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 3:12 XFS Fails Quality Assurance Tests on ARM Byron Bradley
2007-08-31 4:39 ` David Miller
2007-09-01 22:14 ` Andi Kleen
2007-09-27 21:40 ` Nick Piggin
2007-10-02 7:38 ` David Chinner
2007-10-30 5:47 ` Eric Sandeen [this message]
2007-10-30 17:54 ` Christoph Hellwig
2007-10-30 18:14 ` Eric Sandeen
2007-10-30 21:38 ` David Miller
2008-03-18 3:41 ` Eric Sandeen
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=4726C577.9000209@sandeen.net \
--to=sandeen@sandeen.net \
--cc=andi@firstfloor.org \
--cc=byron.bbradley@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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