On Tuesday 17 November 2009, Theodore Tso wrote: > 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 : http://bugzilla.kernel.org/show_bug.cgi?id=14354 > > Subject : Bad corruption with 2.6.32-rc1 and upwards > > Submitter : Holger Freyther <[email protected]> > > 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?
I wasn't quite sure what the status was, because there was some activity in the bug entry after it had been marked as resolved. > 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. OK, great, thanks for the confirmation. I'll close it now. Best, Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
