This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: C11 threads ABI questions - enum values
- From: Christoph Hellwig <hch at lst dot de>
- To: Rich Felker <dalias at libc dot org>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Roland McGrath <roland at hack dot frob dot com>, libc-alpha at sourceware dot org
- Date: Thu, 23 Oct 2014 18:58:18 +0200
- Subject: Re: C11 threads ABI questions - enum values
- Authentication-results: sourceware.org; auth=none
- References: <20141003183910 dot GA8806 at lst dot de> <20141003194932 dot GU23797 at brightrain dot aerifal dot cx> <20141004175346 dot GA23717 at lst dot de> <20141004225756 dot GV23797 at brightrain dot aerifal dot cx> <20141005094913 dot GA7947 at lst dot de> <20141005161358 dot GW23797 at brightrain dot aerifal dot cx> <20141005162317 dot GA12566 at lst dot de> <20141023080034 dot GA29298 at lst dot de> <20141023163723 dot GE22465 at brightrain dot aerifal dot cx> <20141023163833 dot GF22465 at brightrain dot aerifal dot cx>
On Thu, Oct 23, 2014 at 12:38:33PM -0400, Rich Felker wrote:
> > I've got a lot of things I'm working on at the moment, but I'll try to
> > give it a test maybe early next week. Is that soon enough?
>
> Hmm, looking again it looks like it's not so much a matter of testing
> the patch as verifying that there are no other missing cases. Is that
> right? Let me know if I'm misunderstanding what you want.
I'm pretty sure that patch works for those two syscalls, but independent
verification is always welcome. The more important bit would be a list
of remaining workaround you have to implement O_SEARCH (I think that should be
it) and O_EXEC. For O_EXEC I suspect right now you don't have any other
workaround either given the /proc based fexecve implementation, but just
at the same time we're now getting a syscall for that one, so we'll have
to take care of that. For O_EXEC with a syscall-based fexecve we'll
probably need the O_PATH|3 defintion and some hacky looking code in the
kernel I fear, so it would be great if you could bring that up in the
current discussion of the execveat system call.