From patchwork Tue Oct 30 19:27:57 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Theodore Ts'o X-Patchwork-Id: 195611 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 2FD792C007D for ; Wed, 31 Oct 2012 06:28:09 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933167Ab2J3T2G (ORCPT ); Tue, 30 Oct 2012 15:28:06 -0400 Received: from li9-11.members.linode.com ([67.18.176.11]:58512 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932654Ab2J3T2E (ORCPT ); Tue, 30 Oct 2012 15:28:04 -0400 Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.72) (envelope-from ) id 1TTHTg-0003v7-IQ; Tue, 30 Oct 2012 19:27:56 +0000 Received: by closure.thunk.org (Postfix, from userid 15806) id 9C60C2479E0; Tue, 30 Oct 2012 15:27:57 -0400 (EDT) From: Theodore Ts'o To: Linus Torvalds Cc: linux-ext4@vger.kernel.org Subject: [GIT PULL] more ext4 bug fixes for 3.7 Subject: Date: Tue, 30 Oct 2012 15:27:57 -0400 Message-ID: MIME-Version: 1.0 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@mit.edu X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org The following changes since commit 8f0d8163b50e01f398b14bcd4dc039ac5ab18d64: Linux 3.7-rc3 (2012-10-28 12:24:48 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable for you to fetch changes up to ffb5387e85d528fb6d0d924abfa3fbf0fc484071: ext4: fix unjournaled inode bitmap modification (2012-10-28 22:24:57 -0400) ---------------------------------------------------------------- This fixes the root cause of the ext4 data corruption bug which raised a ruckus on LWN, Phoronix, and Slashdot. This bug only showed up when non-standard mount options (journal_async_commit and/or journal_checksum) were enabled, and when the file system was not cleanly unmounted, but the root cause was the inode bitmap modifications was not being properly journaled. This could potentially lead to minor file system corruptions (pass 5 complaints with the inode allocation bitmap) after an unclean shutdown under the wrong/unlucky workloads, but it turned into major failure if the journal_checksum and/or jouaral_async_commit was enabled. ---------------------------------------------------------------- Eric Sandeen (1): ext4: fix unjournaled inode bitmap modification fs/ext4/ialloc.c | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) --- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html