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, 26 Mar 2009 02:24:16 -0400 From: Jeff Garzik <jeff@...zik.org> To: Kyle Moffett <kyle@...fetthome.net> CC: Linus Torvalds <torvalds@...ux-foundation.org>, Matthew Garrett <mjg59@...f.ucam.org>, Theodore Tso <tytso@....edu>, Christoph Hellwig <hch@...radead.org>, Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>, Arjan van de Ven <arjan@...radead.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Nick Piggin <npiggin@...e.de>, Jens Axboe <jens.axboe@...cle.com>, David Rees <drees76@...il.com>, Jesper Krogh <jesper@...gh.cc>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 2.6.29 Kyle Moffett wrote: > Really, I think virtually all of the database programs would be > perfectly happy with an "fsbarrier(fd, flags)" syscall, where if "fd" > points to a regular file or directory then it instructs the underlying > filesystem to do whatever internal barrier it supports, and if not > just fail with -ENOTSUPP (so you can fall back to fdatasync(), etc). > Perhaps "flags" would allow a "data" or "metadata" barrier, but if not > it's not a big issue. If you want a per-fd barrier call, there is always sync_file_range(2) > If a user-level tool needs to enforce ordering > between IOs the only tool right now is is a full flush or sync_file_range(2)... Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists