| 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, 10 Jun 2011 10:29:07 -0700 From: Darren Hart <dvhart@...ux.intel.com> To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> CC: peterz@...radead.org, eric.dumazet@...il.com, david@...advisors.com, linux-kernel@...r.kernel.org, sbohrer@...advisors.com, zvonler@...advisors.com, hughd@...gle.com, tglx@...utronix.de, mingo@...e.hu Subject: Re: Change in functionality of futex() system call. On 06/10/2011 05:10 AM, KOSAKI Motohiro wrote: > > Off topic: current futex documentations are near terribly unclear and > many futex op are completely undocumented. They are one of root cause > that every change can make compatibility issue. (;_; What documentation are you referring to? The futex man page is a wreck, and I'm not sure what to do with it since glibc removed the futex() call. You now have to wrap the syscall manually anyway. If you are referring to the futex.c file itself, I have been documenting functions as I modify them. If you found any of those lacking, please let me know which ones and I'll try to clean them up. If you're referring to those that remain undocumented, please send a doc patch and I'll review and help get it upstream. I'd like to see this improved as well. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel -- 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