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, 16 Apr 2009 10:44:30 +0200 From: Jan Kara <jack@...e.cz> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Chris Mason <chris.mason@...cle.com>, Theodore Ts'o <tytso@....edu>, Linux Kernel Developers List <linux-kernel@...r.kernel.org>, Ext4 Developers List <linux-ext4@...r.kernel.org> Subject: Re: [PATCH RFC] ext3 data=guarded v3 On Wed 15-04-09 13:35:23, Linus Torvalds wrote: > > > On Wed, 15 Apr 2009, Chris Mason wrote: > > > > Here is another version of the data=guarded work for ext3. The main > > difference between this code and yesterday's is the guarded writepage > > function now sends any newly allocated block through the old data=ordered code. > > I'm inclined to apply the first two patches as infrastructure, since they > seem to make sense regardless of data=ordered. The ability to get a > callback when IO ends sounds like something that a number of cases might > find intriguing, and it's obviously how the actual IO has worked > internally anyway. > > Comments? Yes, the first two patches look fine to me. I tried to review the third patch yesterday but my mind has blown up when trying to track all the possible interactions and I started doing something else to preserve last bits of sanity ;). Will retry later... Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- 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