From: Dave Chinner <david@fromorbit.com>
To: Mario Bachmann <mbachman@stud.uni-frankfurt.de>, xfs@oss.sgi.com
Subject: Re: [PATCH] Re: xfsdump-3.0.4 problems
Date: Fri, 27 Aug 2010 21:40:55 +1000 [thread overview]
Message-ID: <20100827114055.GI705@dastard> (raw)
In-Reply-To: <20100827111820.GA9837@teal.hq.k1024.org>
On Fri, Aug 27, 2010 at 01:18:20PM +0200, Iustin Pop wrote:
> On Tue, Aug 17, 2010 at 09:45:50PM +1000, Dave Chinner wrote:
> > My fault. I screwed up the btree lookup for the inode validation.
> > Can you test the patch below?
>
> I just see that 2.6.35.4 has been released, but it doesn't include this
> fix (as far as I can see). Could it be send for inclusion into the next
> stable please (yes, it fixes the issue for me too).
The commit is now upstream, it had a "cc: stable@kernel.org" in it,
so it should get automatically queued for inclusion in the next
stable kernel release. If I don't see it appear in Greg's stable
queue once he starts processing the commits for the next stable
release, I'll chase it up....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-27 11:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 16:22 xfsdump-3.0.4 problems Mario Bachmann
2010-08-16 22:30 ` Dave Chinner
2010-08-17 6:32 ` Mario Bachmann
2010-08-17 7:13 ` Dave Chinner
2010-08-17 7:53 ` Mario Bachmann
2010-08-17 9:05 ` Dave Chinner
2010-08-17 11:45 ` [PATCH] " Dave Chinner
2010-08-17 15:47 ` Mario Bachmann
2010-08-18 10:10 ` Christoph Hellwig
2010-08-27 11:18 ` Iustin Pop
2010-08-27 11:40 ` Dave Chinner [this message]
2010-09-24 9:53 ` Mario Bachmann
2010-10-03 6:20 ` Christoph Hellwig
2010-08-17 9:03 ` 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=20100827114055.GI705@dastard \
--to=david@fromorbit.com \
--cc=mbachman@stud.uni-frankfurt.de \
--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