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, 8 Mar 2012 16:41:48 -0500 From: Ted Ts'o <tytso@....edu> To: Chris Mason <chris.mason@...cle.com>, Boaz Harrosh <bharrosh@...asas.com>, Zach Brown <zab@...bo.net>, Eric Sandeen <sandeen@...hat.com>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org Subject: Re: [PATCH, RFC] Don't do page stablization if !CONFIG_BLKDEV_INTEGRITY On Thu, Mar 08, 2012 at 04:38:08PM -0500, Chris Mason wrote: > Btrfs currently does this, and the DIF code is by definition right > before the write. The pages really only get set writeback when they are > being sent in flight, so the waiting being done by the stable pages > patch is file_write or page_mkwrite being polite and waiting for the IO > to finish before changing the page. Right before submission to the bio layer? Or right before the device driver sends the request to the host bus adapter? I was thinking of the latter.... - 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