From: Kerin Millar <kerframil@fastmail.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug
Date: Fri, 02 Nov 2012 16:08:23 +0000 [thread overview]
Message-ID: <5093EFF7.70407@fastmail.co.uk> (raw)
In-Reply-To: <5093DEEE.6050909@gmail.com>
Dale wrote:
> Kerin Millar wrote:
>> Helmut Jarausch wrote:
>>> On 10/24/2012 03:54:39 PM, Nikos Chantziaras wrote:
>>>> Kernels 3.4, 3.5, and 3.6 can result in severe data corruption if
>>>> you're using the EXT4 filesystem:
>>> It looks as if Eric Sandeen has found the culprit and Theodore Ts'o has
>>> suggested this patch yesterday
>>> https://lkml.org/lkml/2012/10/28/309
>>>
>>> Helmut.
>>>
>> Here's the final patch:
>>
>> https://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ffb5387
>>
>>
>> It turns out to have had nothing to do with nobarrier.
>>
>> --Kerin
>>
>>
>
>
> Could you explain a little on who it could have affected? Is it more
> serious or less serious than originally thought? This is for those of
> us who don't subscribe to the kernel mailing list, which I have read is
> hugely active.
I would describe the bug itself as serious but it will affect few users
because journal_checksum isn't enabled by default. Ted submitted a patch
to enable the option by default back in 2009 but it was reverted a few
months later by Linus due to this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=14354
I'm pretty sure that it hasn't since been re-enabled as a default. As
long as you haven't enabled this option, you shouldn't have anything to
worry about.
--Kerin
next prev parent reply other threads:[~2012-11-02 16:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 13:54 [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug Nikos Chantziaras
2012-10-24 14:42 ` Dale
2012-10-24 15:22 ` covici
2012-10-24 14:43 ` Paul Hartman
2012-10-24 14:48 ` Markos Chandras
2012-10-24 18:10 ` Bruce Hill
2012-10-24 22:36 ` john
2012-10-24 23:55 ` mindrunner
2012-10-25 0:55 ` Canek Peláez Valdés
2012-10-25 1:09 ` Kerin Millar
2012-10-25 1:32 ` Canek Peláez Valdés
2012-10-25 1:38 ` Canek Peláez Valdés
2012-10-25 2:51 ` Kerin Millar
2012-10-25 3:03 ` Michael Mol
2012-10-25 19:40 ` Pandu Poluan
2012-10-25 20:10 ` Dale
2012-10-26 0:34 ` Neil Bothwick
2012-10-26 8:29 ` Dale
2012-10-27 19:16 ` Volker Armin Hemmann
2012-10-28 17:12 ` Mark Knecht
2012-10-26 3:26 ` Pandu Poluan
2012-10-26 8:16 ` Dale
2012-10-25 20:33 ` Mark Knecht
2012-10-26 3:30 ` Pandu Poluan
2012-10-25 23:10 ` Michael Mol
2012-10-26 3:37 ` Pandu Poluan
2012-10-25 3:04 ` Canek Peláez Valdés
2012-10-25 4:43 ` [gentoo-user] " Nikos Chantziaras
2012-10-25 14:26 ` Grant Edwards
2012-10-25 16:53 ` Remy Blank
2012-10-25 21:04 ` Kerin Millar
2012-10-27 18:19 ` Volker Armin Hemmann
2012-10-27 18:28 ` Canek Peláez Valdés
2012-10-29 10:29 ` [gentoo-user] " Helmut Jarausch
2012-11-02 13:45 ` Kerin Millar
2012-11-02 14:55 ` Dale
2012-11-02 15:05 ` Michael Mol
2012-11-02 15:08 ` Paul Hartman
2012-11-02 16:08 ` Kerin Millar [this message]
2012-11-02 20:19 ` Dale
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=5093EFF7.70407@fastmail.co.uk \
--to=kerframil@fastmail.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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