From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
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 13:14:29 -0500 [thread overview]
Message-ID: <47277485.5090500@sandeen.net> (raw)
In-Reply-To: <20071030175418.GA17768@infradead.org>
Christoph Hellwig wrote:
> On Tue, Oct 30, 2007 at 12:47:35AM -0500, Eric Sandeen wrote:
>> 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.
>
> Do you have a pointer to that patch? Once the unaliged fields are
> identified simply using get_unaligned on them should fix this issue.
>
http://www.spinics.net/lists/arm-kernel/msg18479.html
is the one I was thinking of, IIRC, but it just does the math a
different way so that it comes out right on ARM, and doesn't fix the
underlying problem. I think the end result is no crashes, but a
filesystem which is broken when used on another arch.
But the problem AFAIK is that the *on-disk* structures don't match when
compiled with one ARM abi or another, I think, so get_unaligned isn't
going to help here.
-Eric
next prev parent reply other threads:[~2007-10-30 18:14 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
2007-10-30 17:54 ` Christoph Hellwig
2007-10-30 18:14 ` Eric Sandeen [this message]
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=47277485.5090500@sandeen.net \
--to=sandeen@sandeen.net \
--cc=andi@firstfloor.org \
--cc=byron.bbradley@gmail.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--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