This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Jeff Layton <jlayton at redhat dot com>
- Cc: libc-alpha at sourceware dot org, linux-fsdevel at vger dot kernel dot org
- Date: Wed, 12 Feb 2014 15:19:53 -0800 (PST)
- Subject: Re: [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values
- Authentication-results: sourceware.org; auth=none
- References: <1392145436-13983-1-git-send-email-jlayton at redhat dot com> <1392145436-13983-2-git-send-email-jlayton at redhat dot com> <20140211214915 dot 2FB4774438 at topped-with-meat dot com> <20140211185748 dot 378c67f0 at corrin dot poochiereds dot net>
> My plan is to eventually submit this to become part of the POSIX
> standard though they won't take it until there's at least one shipping
> implementation. I assume that we just need to stick that inside of
> __USE_GNU for now, and if POSIX eventually picks it up then we'll just
> remove that protection?
Change it as appropriate, yes.
> Why does glibc have its own definitions for the fcntl F_* cmd values
> instead of using the ones in the uapi kernel headers? Would it not be
> simpler to just have the fcntl.h include those instead of duplicating
> them?
libc headers respect ISO C and POSIX name space constraints.
Kernel headers (even uapi ones) fail to.