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
| ||
|
Message-ID: <20101212023415.GG3059@thunk.org> Date: Sat, 11 Dec 2010 21:34:15 -0500 From: Ted Ts'o <tytso@....edu> To: Jon Nelson <jnelson@...poni.net> Cc: Matt <jackdachef@...il.com>, Chris Mason <chris.mason@...cle.com>, Andi Kleen <andi@...stfloor.org>, Mike Snitzer <snitzer@...hat.com>, Milan Broz <mbroz@...hat.com>, linux-btrfs <linux-btrfs@...r.kernel.org>, dm-devel <dm-devel@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, htd <htd@...cy-poultry.org>, htejun <htejun@...il.com>, linux-ext4 <linux-ext4@...r.kernel.org> Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective) One experiment --- can you try this with the file system mounted with data=writeback, and see if the problem reproduces in that journalling mode? I want to rule out (if possible) journal_submit_inode_data_buffers() racing with mpage_da_submit_io(). I don't think that's the issue, but I'd prefer to do the experiment to make sure. So if you can use a kernel and system configuration which triggers the problem, and then try changing the mount options to include data=writeback, and then rerun the test, and let me know if the problem still reproduces, I'd be really grateful. Thanks, - Ted -- 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