| 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, 11 Apr 2007 12:52:56 -0700 From: Zach Brown <zach.brown@...cle.com> To: Benjamin LaHaise <bcrl@...ck.org> Cc: Ken Chen <kenchen@...gle.com>, akpm@...ux-foundation.org, linux-aio@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [patch] convert aio event reap to use atomic-op instead of spin_lock > > I kept on getting requests from application developers who want that > > feature. My initial patch was dated back May 2004. > > The right way to do it involves synchronization between the kernel side > io_getevents() and the userspace code pulling events out of the ring. > Alan Cox suggested embedding a futex in the shared memory region, but I > don't think anyone ever implemented that. Yeah, I like the idea of futexes. I'm worried that virtual aliasing spells doom for the current home-brewed serialization that fs/aio.c is doing with the shared ring head/tail accesses. Am I worrying about nothing here? > > I will look into this aside from this patch. > > That's probably the case. Also, any changes in this area *must* correctly > update the compat/incompat feature flags in the ring buffer header. That > has been missed in the past... Do you know of anyone using the current ring info ABI? The *only* user I know of is the check of ctx->magic in libaio. - z - 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