public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	xfs-masters@oss.sgi.com, David Chinner <dgc@sgi.com>,
	Christoph Lameter <clameter@sgi.com>,
	tes@sgi.com
Subject: Re: 2.6.22-rc2: known regressions with patches
Date: Mon, 28 May 2007 11:15:02 +1000	[thread overview]
Message-ID: <20070528011502.GW85884050@sgi.com> (raw)
In-Reply-To: <4658D26C.9010803@goop.org>

On Sun, May 27, 2007 at 01:35:56AM +0100, Jeremy Fitzhardinge wrote:
> Michal Piotrowski wrote:
> > File systems
> >
> > Subject    : 2.6.21-git10/11: files getting truncated on xfs
> > References : http://lkml.org/lkml/2007/5/9/410
> > Submitter  : Jeremy Fitzhardinge <jeremy@goop.org>
> > Handled-By : David Chinner <dgc@sgi.com>
> > Patch      : http://lkml.org/lkml/2007/5/12/93
> > Status     : patch available
> >   
> 
> I'm satisfied the patch fixes the problem for me.  Can we have some
> movement to get it into at least -mm?  This is a real, serious
> data-corrupting bug.  Ideally we should get it into -rc asap.

Patience, please. We like to have some QA coverage on a changes that
affect the writeback path in such a subtle manner before saying it
is good to go. Just releasing the fix into the main tree would be
irresponsible as there is the real possibility of the fix causing
other subtle corruption problems.

The fact the fix Works For You doesn't mean it works for everyone so
we need to take the time to make sure the fix is correct rather than
doing a half-arsed job of it and potentially leaving a landmine that
explodes on the wider community after release.

That being said, the fix doesn't appear to have any landmines in
it so we'll be pushing it to Linus RSN...

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-05-28  1:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 14:04 2.6.22-rc2: known regressions with patches Michal Piotrowski
2007-05-24 15:11 ` Alan Cox
2007-05-24 16:54   ` Andrew Morton
2007-05-27  0:35 ` Jeremy Fitzhardinge
2007-05-28  1:15   ` David Chinner [this message]
2007-05-29 20:13     ` Jeremy Fitzhardinge
2007-06-04 21:04 ` Fabio Comolli

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=20070528011502.GW85884050@sgi.com \
    --to=dgc@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=tes@sgi.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xfs-masters@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