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: Tue, 20 May 2008 21:54:37 +0200 From: Jens Axboe <jens.axboe@...cle.com> To: Theodore Tso <tytso@....edu>, Eric Sandeen <sandeen@...hat.com>, ext4 development <linux-ext4@...r.kernel.org>, linux-kernel Mailing List <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH 4/4] ext4: call blkdev_issue_flush on fsync On Tue, May 20 2008, Jamie Lokier wrote: > Does WRITE_BARRIER always cause a flush? It does not have to > according to Documentation/block/barrier.txt. There are caveats about > tagged queuing "not yet implemented" in the text, but can we rely on > that? The documentation is older than the current implementation; > those caveats might no longer apply. It does, if you use ordered tags then that assumes write through caching (or ordered tag + drain + flush after completion). -- Jens Axboe -- 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