From: Roland McGrath Subject: Re: [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values Date: Wed, 12 Feb 2014 15:19:53 -0800 (PST) Message-ID: <20140212231953.EB16974417@topped-with-meat.com> References: <1392145436-13983-1-git-send-email-jlayton@redhat.com> <1392145436-13983-2-git-send-email-jlayton@redhat.com> <20140211214915.2FB4774438@topped-with-meat.com> <20140211185748.378c67f0@corrin.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: libc-alpha@sourceware.org, linux-fsdevel@vger.kernel.org To: Jeff Layton Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: Jeff Layton's message of Tuesday, 11 February 2014 18:57:48 -0500 <20140211185748.378c67f0@corrin.poochiereds.net> List-Id: linux-fsdevel.vger.kernel.org > 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.