lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070528011502.GW85884050@sgi.com>
Date:	Mon, 28 May 2007 11:15:02 +1000
From:	David Chinner <dgc@....com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, xfs-masters@....sgi.com,
	David Chinner <dgc@....com>,
	Christoph Lameter <clameter@....com>, tes@....com
Subject: Re: 2.6.22-rc2: known regressions with patches

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@...p.org>
> > Handled-By : David Chinner <dgc@....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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ