| 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: Mon, 12 Apr 2010 14:54:03 +0200 From: Pavel Machek <pavel@....cz> To: Michael Schnell <mschnell@...ino.de> Cc: David Newall <davidn@...idnewall.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: atomic RAM ? Hi! > OTOH, to do FUTEX in full (MMU) - Linux, atomic operations are > definitively necessary, as in Userland you can't disable the interrupt > without a Kernel call (which to avoid FUTEX is all about.) Currently the You could create unpriviledged 'disable interrupts for 10 instructions' and 'test if interrupts are still disabled' instructions, and base your mutex implementation on that. But you'll have to stop calling it futex at that point... Or you could just optimize syscalls to be really fast... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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