From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B4290138010 for ; Fri, 2 Nov 2012 15:11:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3471721C0BB; Fri, 2 Nov 2012 15:11:31 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 5CE5D21C0B8 for ; Fri, 2 Nov 2012 15:09:10 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id gg6so2660057lbb.40 for ; Fri, 02 Nov 2012 08:09:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=HZBTRpvATP/zINw7mOf7X+Cj0mfCSxR6igVDz5/qHvI=; b=vPWcet+Y3VggptVDSnQcB1hg0HJc5vqDwESiHzoaAbPF12FVXoYbpcE6j6TpYT6ZbE +NM72xq8509rlAh9MsqsU6nQSiRbZbZcVwexkmFQiYVfdKWZIuH73om4XayimRhIs1ix GK8f4dmWfB2Nw9ZALa+Xp2XS7tajy9jVk2U/ZBDgztF2Bh8uXPnLQLfrysekZz9hWojG 1RQgpTAPejYpxukgw4NgLy19RPr170/vmwfuoj9qFA54Xj04oGIRs/tUmMzkolD9nm4l jF6NWcJWmVbCJAgrPNm8RwYWRqK5N6aN21u8rXfpr/JFRLsJtEL6UomrCwjuDFWu8F/Y OYNg== Received: by 10.152.105.44 with SMTP id gj12mr1961494lab.19.1351868950072; Fri, 02 Nov 2012 08:09:10 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Sender: paul.hartman@gmail.com Received: by 10.112.9.9 with HTTP; Fri, 2 Nov 2012 08:08:49 -0700 (PDT) In-Reply-To: <5093DEEE.6050909@gmail.com> References: <1351506571.3134.1@numa-i> <5093CE6E.2090707@fastmail.co.uk> <5093DEEE.6050909@gmail.com> From: Paul Hartman Date: Fri, 2 Nov 2012 10:08:49 -0500 X-Google-Sender-Auth: pNwSGLrKQewsEpPRZy34y9TEyvM Message-ID: Subject: Re: [gentoo-user] Heads-up: Several kernel versions have severe EXT4 data corruption bug To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: ac509655-6ece-4324-b8ba-dcd5bbb7daf2 X-Archives-Hash: 9c64550c7422b57ed76a46a31f2503c2 On Fri, Nov 2, 2012 at 9:55 AM, 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. > > Thanks much. AFAIK they originally thought it was related to normal reboots after short uptime, which would potentially put all ext4 users at risk who use newer kernels. That is when the news stories came out about the disastrous ext4 bug. As it turns it, it seems to have been related to enabling some combination of experimental, non-default mount options with an unsafe shutdown cherry on top. So the number of people who are using that would be far, far fewer than they originally thought. Still a dangerous bug for those people, of course, but I would guess probably 99+ percent of ext4 users weren't at risk from it. That is my layman's understanding, I probably got it all wrong. Experts, feel free to correct me. :)