From: Dave Chinner <david@fromorbit.com>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
LKML <linux-kernel@vger.kernel.org>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Thu, 22 Jan 2009 09:58:00 +1100 [thread overview]
Message-ID: <20090121225800.GO10158@disturbed> (raw)
In-Reply-To: <4976E524.1050607@gmail.com>
On Wed, Jan 21, 2009 at 10:04:36AM +0100, Jacek Luczak wrote:
> Dave Chinner pisze:
> > Please try the patch I posted this morning - it fixes the problem
> > properly and shouldn't have this side effect.
>
> Your patch work for me. I've made also some tests a'la one proposed by
> Christoph, here also everything works. Good work guys!
Thanks for testing the fix, Jacek. I'll get it pushed upstream
now.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2009-01-21 22:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 11:49 [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO Jacek Luczak
2009-01-19 18:44 ` Eric Sandeen
2009-01-20 0:46 ` Dave Chinner
2009-01-20 9:26 ` Jacek Luczak
2009-01-20 11:29 ` Christoph Hellwig
2009-01-20 11:47 ` Jacek Luczak
2009-01-20 11:49 ` Christoph Hellwig
2009-01-20 12:13 ` Christoph Hellwig
2009-01-20 12:45 ` Christoph Hellwig
2009-01-20 13:58 ` Jacek Luczak
2009-01-20 14:05 ` Christoph Hellwig
2009-01-20 14:13 ` Jacek Luczak
2009-01-20 14:23 ` Jacek Luczak
2009-01-20 14:32 ` Christoph Hellwig
2009-01-21 4:05 ` Dave Chinner
2009-01-21 9:04 ` Jacek Luczak
2009-01-21 22:58 ` Dave Chinner [this message]
2009-01-20 13:35 ` Dave Chinner
2009-01-20 23:03 ` [PATCH] " Dave Chinner
2009-01-20 23:22 ` Christoph Hellwig
2009-01-20 9:24 ` Jacek Luczak
2009-01-20 10:42 ` Jacek Luczak
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=20090121225800.GO10158@disturbed \
--to=david@fromorbit.com \
--cc=difrost.kernel@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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;
as well as URLs for NNTP newsgroup(s).