From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darren Hart Subject: Re: futex(2) man page update help request Date: Wed, 14 May 2014 22:21:52 -0700 Message-ID: References: <537346E5.4050407@gmail.com> <537407ED.8050606@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <537407ED.8050606-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "H. Peter Anvin" , "Michael Kerrisk (man-pages)" , Thomas Gleixner , Ingo Molnar , Jakub Jelinek Cc: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , lkml , Davidlohr Bueso , Arnd Bergmann , Steven Rostedt , Peter Zijlstra , Linux API , Carlos O'Donell List-Id: linux-man@vger.kernel.org On 5/14/14, 17:18, "H. Peter Anvin" wrote: >On 05/14/2014 09:18 AM, Darren Hart wrote: >> >> However, unless I'm sorely mistaken, the larger problem is that glibc >> removed the futex() call entirely, so these man pages don't describe >> something users even have access to anymore. I had to revert to calling >> the syscalls directly in the futextest test suite because of this: >> >> >>http://git.kernel.org/cgit/linux/kernel/git/dvhart/futextest.git/tree/inc >>lu >> de/futextest.h#n67 >> > >This really comes down to the fact that we should have a libinux which >contains the basic system call wrapper machinery for Linux specific >things and nothing else. > >syscall(3) is toxic and breaks randomly on some platforms. Peter Z and I have had a good time discussing this in the past.... And here it is again. :-) -- Darren Hart Open Source Technology Center darren.hart-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Intel Corporation -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html