public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <dchinner@redhat.com>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Ben Myers <bpm@sgi.com>, stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix attr tree double split corruption
Date: Fri, 23 Nov 2012 11:49:37 +1100	[thread overview]
Message-ID: <20121123004937.GC18889@devil.redhat.com> (raw)
In-Reply-To: <1353625175-29479-1-git-send-email-peterhuewe@gmx.de>

[added xfs@oss.sgi.com]

On Thu, Nov 22, 2012 at 11:59:35PM +0100, Peter Huewe wrote:
> In certain circumstances, a double split of an attribute tree is
> needed to insert or replace an attribute. In rare situations, this
> can go wrong, leaving the attribute tree corrupted. In this case,
> the attr being replaced is the last attr in a leaf node, and the
> replacement is larger so doesn't fit in the same leaf node.
> When we have the initial condition of a node format attribute
> btree with two leaves at index 1 and 2. Call them L1 and L2.  The
> leaf L1 is completely full, there is not a single byte of free space
> in it. L2 is mostly empty.  The attribute being replaced - call it X
> - is the last attribute in L1.

Hi Peter,

While I appreciate what you are doing here, can you please send
stable backport patches to the xfs@oss.sgi.com list for review
before sending them to stable@vger.kernel.org? There may already be
someone doing this work, and we want to make sure that backports are
correct, tested and worth the risk of fixing before asking the
(already overworked) stable kernel maintainers to include it.

As such, how did you test that the fix works on the stable kernels
you are targetting? AFAIK, I'm the only person who has the
filesystem images that reproducably triggered this corruption
problem....

> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> Reviewed-by: Mark Tinguely <tinguely@sgi.com>
> Signed-off-by: Ben Myers <bpm@sgi.com>
> 
> Cc: <stable@vger.kernel.org> # 3.6.x
> Cc: <stable@vger.kernel.org> # 3.4.x
> Cc: <stable@vger.kernel.org> # 3.2.x

If we are pushing this fix back to stable kernels, then it
should go back to 3.0.x as well.

Cheers,

Dave.
-- 
Dave Chinner
dchinner@redhat.com

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

       reply	other threads:[~2012-11-23  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1353625175-29479-1-git-send-email-peterhuewe@gmx.de>
2012-11-23  0:49 ` Dave Chinner [this message]
2012-11-23  7:32   ` [PATCH] xfs: fix attr tree double split corruption Peter Hüwe
2012-11-23  8:55     ` Dave Chinner
2012-11-07  6:06 Dave Chinner

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=20121123004937.GC18889@devil.redhat.com \
    --to=dchinner@redhat.com \
    --cc=bpm@sgi.com \
    --cc=peterhuewe@gmx.de \
    --cc=stable@vger.kernel.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