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: Wed, 31 Jan 2007 12:37:21 +0300 From: Michael Tokarev <mjt@....msk.ru> To: Phillip Susi <psusi@....rr.com> CC: Andrea Arcangeli <andrea@...e.de>, Denis Vlasenko <vda.linux@...glemail.com>, Bill Davidsen <davidsen@....com>, Linus Torvalds <torvalds@...l.org>, Viktor <vvp01@...ox.ru>, Aubrey <aubreylee@...il.com>, Hua Zhong <hzhong@...il.com>, Hugh Dickins <hugh@...itas.com>, Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: O_DIRECT question Phillip Susi wrote: [] > You seem to have missed the point of this thread. Denis Vlasenko's > message that you replied to simply pointed out that they are > semantically equivalent, so O_DIRECT can be dropped provided that O_SYNC > + madvise could be fixed to perform as well. Several people including > Linus seem to like this idea and think it is quite possible. By the way, IF O_SYNC+madvise could be "fixed", can't O_DIRECT be implemented internally using them? I mean, during open(O_DIRECT), do open(O_SYNC) instead and call madvise() appropriately.... /mjt - 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