linux-ext4 - [PATCH 0/2] Patch to address the ext4 corruption problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Oct 2012 16:00:59 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Cc:	sandeen@...hat.com, Theodore Ts'o <tytso@....edu>
Subject: [PATCH 0/2] Patch to address the ext4 corruption problem

This is the patch series I propose to send to Linus after I get
confirmation from either Toralf or Nix that this fixes the increased
incidence rate of this problem to pre-3.6.2 levels.  (Nix has found a
way to reproduce the problem with 3.6.1, but it seems that it's much
more easy with 3.6.2 and 3.6.3.)

The second patch fixes the problem which the original commit is
attempting to address, but in a way which does not change jbd2's
behavior in the case where the journal block device is not read/only.

Please review/comment/test; thanks!!

Theodore Ts'o (2):
  ext4: revert "jbd2: don't write superblock when if its empty"
  ext4: fix I/O error when unmounting an ro file system

 fs/jbd2/journal.c | 21 +++++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)

-- 
1.7.12.rc0.22.gcdd159b

--
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