public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias Frost <tobi@coldtobi.de>
To: Gaudenz Steinlin <gaudenz@debian.org>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	linux-kernel@vger.kernel.org, debian-arm@lists.debian.org,
	xfs@oss.sgi.com
Subject: Re: XFS filesystem corruption on the arm(el) architecture
Date: Sat, 18 Oct 2008 15:11:14 +0200	[thread overview]
Message-ID: <1224335474.8763.1.camel@moria> (raw)
In-Reply-To: <20081017094615.GT4504@soziologie.ch>

I tried xfs both on the old and new ABI.
(my first try was Jan 2008, old ABI) 
ASAIR at kernel version 2.6.18

On Fri, 2008-10-17 at 11:46 +0200, Gaudenz Steinlin wrote:
> On Fri, Oct 17, 2008 at 09:01:09AM +0200, Martin Michlmayr wrote:
> > * Eric Sandeen <sandeen@sandeen.net> [2008-10-16 17:13]:
> > > So is this a regression?  did it used to work?  If so, when? :)
> > 
> > The original report was with 2.6.18 but that was with the old ABI:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423562
> > I just installed a 2.6.22 kernel with EABI and I can also trigger
> > the bug.  So it's not a (recent) regression.
> 
> As far as I can remember (I only used old ABI arm) this is not a 
> regression. XFS never worked on arm for me.
> 
> If you need tests on old ABI just tell me.
> 

  parent reply	other threads:[~2008-10-18  9:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 20:38 XFS filesystem corruption on the arm(el) architecture Tobias Frost
2008-10-02  0:45 ` Dave Chinner
2008-10-02  0:56   ` Eric Sandeen
2008-10-02  1:17   ` Eric Sandeen
2008-10-16 21:25     ` Martin Michlmayr
2008-10-16 22:13       ` Eric Sandeen
2008-10-17  7:01         ` Martin Michlmayr
2008-10-17  9:46           ` Gaudenz Steinlin
2008-10-17 13:49             ` Eric Sandeen
2008-10-18 13:11             ` Tobias Frost [this message]
2008-10-18 19:48             ` Kirill A. Shutemov
2008-10-18 20:09               ` Christoph Hellwig
2008-10-18 20:17                 ` Kirill A. Shutemov
2008-10-17 14:15           ` Eric Sandeen
2008-10-18  8:57             ` Martin Michlmayr
2008-10-18 14:48               ` Eric Sandeen
2008-10-19  1:48               ` Dave Chinner
2008-10-19  3:06                 ` Eric Sandeen
2008-10-19  9:07                   ` Christoph Hellwig
2008-10-19 16:22                     ` Lennert Buytenhek
2008-10-19  5:12                 ` Martin Michlmayr
2008-10-02  1:42   ` 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=1224335474.8763.1.camel@moria \
    --to=tobi@coldtobi.de \
    --cc=debian-arm@lists.debian.org \
    --cc=gaudenz@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=tbm@cyrius.com \
    --cc=xfs@oss.sgi.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