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
| ||
|
Date: Thu, 25 Oct 2012 12:06:42 +0100 From: Nix <nix@...eri.org.uk> To: "Theodore Ts'o" <tytso@....edu> Cc: Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, "J. Bruce Fields" <bfields@...ldses.org>, Bryan Schumaker <bjschuma@...app.com>, Peng Tao <bergwolf@...il.com>, Trond.Myklebust@...app.com, gregkh@...uxfoundation.org, Toralf Förster <toralf.foerster@....de> Subject: Re: Apparent serious progressive ext4 data corruption bug in 3.6 (when rebooting during umount) On 25 Oct 2012, Theodore Ts'o stated: > Also, can you reproduce the problem with the nobarrier and > journal_async_commit options *removed*? Yes, I know you have battery > backup, but it would be interesting to see if the problem shows up in > the default configuration with none of the more specialist options. > (So it would probably be good to test with journal_checksum removed as > well.) I'm going to spend some time after work today trying to reproduce this in a virtual machine. If rebooting while umounting is truly all it takes, as it seems, this should eliminate a bunch of variables and make it a lot easier to reproduce. (Assuming Eric hasn't already done just that, that is.) -- NULL && (void) -- 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