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: Mon, 19 Jan 2009 07:45:13 -0500 From: Theodore Tso <tytso@....edu> To: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> Cc: linux-ext4@...r.kernel.org Subject: Re: The meaning of data=ordered as it relates to delayed allocation On Mon, Jan 19, 2009 at 10:13:45AM +0530, Aneesh Kumar K.V wrote: > > So I wonder if we should either: > > > > (a) make data=ordered force block allocation and writeback --- which > > should just be a matter of disabling the > > redirty_page_for_writepage() code path in ext4_da_writepage() > > We can't do that because we cannot do block allocation there. So we need > to redirty the page that have unmapped buffer_heads. What is preventing us from doing block allocation from ext4_da_writepage()? - 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