| 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: Fri, 3 Jul 2009 04:14:05 -0400 From: Mike Frysinger <vapier.adi@...il.com> To: Arnd Bergmann <arnd@...db.de> Cc: linux-kernel@...r.kernel.org, Paul Mundt <lethal@...ux-sh.org> Subject: making asm-generic/futex.h completely usable ive been reading up on futexes of late and have been poking around the futex kernel pieces to see what is needed to get Blackfin working with it. Blackfin falls into the "no hardware atomic instructions" category as can easily be seen in our atomic.h: disable interrupts, do load/stores, restore interrupts. my understanding of the futex_atomic_op_inuser() function is that this runs in process context, so this same interrupt trick should work fine. which leads me to wonder why doesnt the asm-generic/futex.h header already take this approach ? seems to me that the SuperH implementation fits the bill nicely. their arch/sh/include/asm/futex-irq.h looks like it could be literally straight copied into asm-generic/futex.h thus making it fully functional for everyone by default. also, the futex_atomic_op_inuser() function itself seems to largely be copy & paste between architectures ... the only differences are in the atomic functions called by FUTEX_OP_XXX. so perhaps the structure of the header should follow that of asm-generic/uaccess.h in that arches can override specific functions while still getting the rest for free ? -mike -- 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