[lkml]   [2009]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bug #14354] Bad corruption with 2.6.32-rc1 and upwards
On Mon, Nov 16, 2009 at 11:37:39PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> The following bug entry is on the current list of known regressions
> from 2.6.31. Please verify if it still should be listed and let me know
> (either way).
> Bug-Entry :
> Subject : Bad corruption with 2.6.32-rc1 and upwards
> Submitter : Holger Freyther <>
> Date : 2009-10-09 15:42 (39 days old)

Um, this was marked as resolved, until you reopened it and then reset
the state to New. Why did you do this?

It's fixed in mainline as of commit d4da6c9 when Linus reverted commit
d0646f7. Users could still see it if they mount a file system with -o
journal_checksum, but (a) it's no longer the default, and (b)
corruption if you use the non-default journal_checksum mount option is
not a regression.

We have fixes to make journal_checksum safe queued for 2.6.33, but the
revert fixes the regression problem.

- Ted

 \ /
  Last update: 2009-11-17 03:09    [W:0.375 / U:0.552 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site