All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfs: fixes for 3.7-rc6
Date: Tue, 13 Nov 2012 15:20:27 -0600	[thread overview]
Message-ID: <20121113212027.GB19387@sgi.com> (raw)
In-Reply-To: <1352718586-3538-1-git-send-email-david@fromorbit.com>

Hi Dave,

On Mon, Nov 12, 2012 at 10:09:43PM +1100, Dave Chinner wrote:
> These are the remaining fixes I have in my tree for the 3.7 cycle.
> One is a corruption fix, the other two are problems I'm seeing
> during shutdown and recovery testing. That testing lasts 400-500
> cycles (3-4 hours) now before it fails with another, as yet unknown
> buffer/perag reference assert failure. Without these fixes, it lasts
> 3-4 cycles before assert failing or triggering a BUG.
> 
> I'd like these fixes to be in the 3.7 cycle if at all possible, with
> both patch 1 and 2 being stable kernel candidates.

committed to git://oss.sgi.com/xfs/xfs.git, master and for-next branches.

I'll send a pull request tomorrow.

Regards,
	Ben

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

      parent reply	other threads:[~2012-11-13 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 11:09 [PATCH 0/3] xfs: fixes for 3.7-rc6 Dave Chinner
2012-11-12 11:09 ` [PATCH 1/3] xfs: fix attr tree double split corruption Dave Chinner
2012-11-12 19:10   ` Mark Tinguely
2012-11-12 11:09 ` [PATCH 2/3] xfs: fix broken error handling in xfs_vm_writepage Dave Chinner
2012-11-13 14:27   ` Mark Tinguely
2012-11-12 11:09 ` [PATCH 3/3] xfs: drop buffer io reference when a bad bio is built Dave Chinner
2012-11-12 20:51   ` Mark Tinguely
2012-11-13  2:01 ` [PATCH 0/3] xfs: fixes for 3.7-rc6 Ben Myers
2012-11-13  3:05   ` Dave Chinner
2012-11-13  7:11     ` Christoph Hellwig
2012-11-13 19:46       ` Dave Chinner
2012-11-13 21:20 ` Ben Myers [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=20121113212027.GB19387@sgi.com \
    --to=bpm@sgi.com \
    --cc=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.