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, 11 Apr 2013 23:18:37 -0400 From: Theodore Ts'o <tytso@....edu> To: Jan Kara <jack@...e.cz> Cc: Zheng Liu <gnehzuil.liu@...il.com>, linux-ext4@...r.kernel.org Subject: Re: [PATCH] ext4: Fix data corruption with direct IO read in dioread_nolock mode On Thu, Apr 11, 2013 at 11:07:56PM +0200, Jan Kara wrote: > Doh, you are right. I didn't notice that. Thanks for correcting me. I was > seeing a failure in xfstest 091 (fsx using direct IO) with dioread_nolock > and I thought the missing flush was the culprit (as fsx saw non-zeros in > the tail of the page that was truncated). After adding the flush I didn't > see it anymore. But now I'm not able to trigger the failure again > regardless whether the patch is applied or not. So Ted, please drop the > patch and I'll watch out if I ever see the failure again. Dropped. - 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