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 Feb 2007 17:06:47 +0100 From: Arjan van de Ven <arjan@...radead.org> To: Trond Myklebust <trond.myklebust@....uio.no> Cc: Benjamin LaHaise <bcrl@...ck.org>, Chris Mason <chris.mason@...cle.com>, "Ananiev, Leonid I" <leonid.i.ananiev@...el.com>, Zach Brown <zach.brown@...cle.com>, linux-aio@...ck.org, linux-kernel@...r.kernel.org, Suparna bhattacharya <suparna@...ibm.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event > We don't try to resolve "conflicting" writes between ordinary mmap() and > write(), so why should we be doing it for mmap and O_DIRECT? > > mmap() is designed to violate the ordinary mutex locks for write(), so > if a conflict arises, whether it be with O_DIRECT or ordinary writes > then it is a case of "last writer wins". but.. wouldn't an O_DIRECT *read* even cause this? - 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