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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 7 Jan 2020 12:11:09 -0500 From: "Theodore Y. Ts'o" <tytso@....edu> To: Jan Kara <jack@...e.cz> Cc: Ritesh Harjani <riteshh@...ux.ibm.com>, Xiaoguang Wang <xiaoguang.wang@...ux.alibaba.com>, Ext4 Developers List <linux-ext4@...r.kernel.org>, joseph.qi@...ux.alibaba.com, Liu Bo <bo.liu@...ux.alibaba.com> Subject: Re: Discussion: is it time to remove dioread_nolock? Hmm..... There's actually an even more radical option we could use, given that Ritesh has made dioread_nolock work on block sizes < page size. We could make dioread_nolock the default, until we can revamp ext4_writepages() to write the data blocks first.... - Ted
Powered by blists - more mailing lists