[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200911172220.nAHMKGj4024388@demeter.kernel.org>
Date: Tue, 17 Nov 2009 22:20:16 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards
http://bugzilla.kernel.org/show_bug.cgi?id=14354
--- Comment #186 from Rafael J. Wysocki <rjw@...k.pl> 2009-11-17 22:20:08 ---
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 <zecke@...fish.org>
> > 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.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists