public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Dave Chinner <dchinner@redhat.com>
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 08:32:44 +0100	[thread overview]
Message-ID: <201211230832.44881.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20121123004937.GC18889@devil.redhat.com>

Hi David,

thanks for your response!
Am Freitag, 23. November 2012, 01:49:37 schrieb Dave Chinner:
> [added xfs@oss.sgi.com]
> 
> On Thu, Nov 22, 2012 at 11:59:35PM +0100, Peter Huewe wrote:
> 
> 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.

Yeah you're right, especially with fs changes we should be more cautious, 
sorry about the noise then.

I'm one of the few people who offered Greg KH a hand after his 'help wanted' 
message/blog post and one of the 'todos' was to look through git-commits@ and 
pick those who look worth of including into stable.

I was probably a bit too eager here, and skimming from top to bottom of git-
commits might also not have been a really good idea either ;)



> 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....

I was mainly looking at:
- does it apply cleanly
- does it still boot
- basic functional test
- short review of the affected code after applying the patch i.e. does it still 
look okay/as intended?

 
> > 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.

3.0.x failed my first test (does it apply cleanly?) so I left it out, as a 
dedicated backport is needed.


Thanks
PeterH



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

  reply	other threads:[~2012-11-23  7:21 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 ` [PATCH] xfs: fix attr tree double split corruption Dave Chinner
2012-11-23  7:32   ` Peter Hüwe [this message]
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=201211230832.44881.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=bpm@sgi.com \
    --cc=dchinner@redhat.com \
    --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