From: David Chinner <dgc@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfsqa 144 is failing now
Date: Fri, 13 Jul 2007 17:17:28 +1000 [thread overview]
Message-ID: <20070713071728.GM31489@sgi.com> (raw)
In-Reply-To: <20070712222304.GA31489@sgi.com>
On Fri, Jul 13, 2007 at 08:23:05AM +1000, David Chinner wrote:
> On Thu, Jul 12, 2007 at 04:04:31PM +0100, Christoph Hellwig wrote:
> > I'm trying to fix up dmapi for the patch that uses filldir internally,
> > and 144 is the xfsqa test for this functionality. It worked fine a
> > few weeks ago when I started that work but fails with plain TOT linux-xfs
> > now with errors like:
.....
> >
> > does anyone have an idea what might be causing this?
>
> Not yet - AFAIK we're only seeing it on i386 ATM, and we only noticed it in
> the past couple of days. Nobody has had a chance to look at it yet. I don't
> think dmapi has been tested regularly on i386 so I'm not sure when the problem
> first appeared yet.
>
> > The only recent changes to xfs_dm.c are the hole punching fixes which
> > seem rather unrelated.
>
> *nod*
>
> Given the expected output, I wouldn't be surprised if we've got
> some kind of 32/64 bit problem here....
Just to confirm - test 144 is passing reliably on ia64 with a TOT
kernel and xfstests, so it's likely to be something specific to i386.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-07-13 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 15:04 xfsqa 144 is failing now Christoph Hellwig
2007-07-12 16:43 ` Justin Piszcz
2007-07-12 16:52 ` Christoph Hellwig
2007-07-12 22:23 ` David Chinner
2007-07-13 7:17 ` David Chinner [this message]
2007-07-26 17:56 ` Christoph Hellwig
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=20070713071728.GM31489@sgi.com \
--to=dgc@sgi.com \
--cc=hch@infradead.org \
--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