public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [GIT PULL] xfs: fixes for 3.15-rc6
Date: Fri, 16 May 2014 16:01:39 +1000	[thread overview]
Message-ID: <20140516060139.GG26353@dastard> (raw)
In-Reply-To: <20140516055320.GA20975@infradead.org>

On Thu, May 15, 2014 at 10:53:20PM -0700, Christoph Hellwig wrote:
> On Fri, May 16, 2014 at 12:11:44PM +1000, Dave Chinner wrote:
> > Hi Linus,
> > 
> > Can you please pull the updates listed below? I found a bunch of
> > error sign issues while determine what we need to do to rid XFS of
> > this problem permanently. A couple of the bugs are in data integirty
> > operations, a couple more are in the new COLLAPSE_RANGE code. One of
> > these came in through a recent ext4 merge and so I had to update the
> > base tree to 3.15-rc5 before fixing the issues.
> 
> Doesn't this miss the log roundin fix?

I'm still verifying/testing that fix (a several day stress
test was need to uncover it in the first place). It will need to be pushed back to
the -stable kernels, anyway, so it doesn't really matter which
kernel it goes into as long as it has the cc: stable tag in it...

> Linus said he is away for about a weeke anyway, while we're at it.

I missed that. Not a big problem, I'll just resend the pull request
when he gets back...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2014-05-16  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  2:11 [GIT PULL] xfs: fixes for 3.15-rc6 Dave Chinner
2014-05-16  5:53 ` Christoph Hellwig
2014-05-16  6:01   ` Dave Chinner [this message]

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=20140516060139.GG26353@dastard \
    --to=david@fromorbit.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