From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH] locks: rename file-private locks to file-description locks Date: Mon, 21 Apr 2014 11:01:20 -0700 Message-ID: <53555CF0.8030405@mit.edu> References: <1398087935-14001-1-git-send-email-jlayton@redhat.com> <20140421140246.GB26358@brightrain.aerifal.cx> <535529FA.8070709@gmail.com> <20140421161004.GC26358@brightrain.aerifal.cx> <20140421124508.4f2c9ca7@tlielax.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: libc-alpha , Carlos O'Donell , samba-technical@lists.samba.org, linux-kernel@vger.kernel.org, "Stefan (metze) Metzmacher" , "Michael Kerrisk (man-pages)" , linux-fsdevel@vger.kernel.org, Ganesha NFS List To: Jeff Layton , Rich Felker Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <20140421124508.4f2c9ca7@tlielax.poochiereds.net> List-Id: linux-fsdevel.vger.kernel.org On 04/21/2014 09:45 AM, Jeff Layton wrote: > On Mon, 21 Apr 2014 12:10:04 -0400 > Rich Felker wrote: >> I'm well aware of that. The problem is that the proposed API is using >> the two-letter abbreviation FD, which ALWAYS means file descriptor and >> NEVER means file description (in existing usage) to mean file >> description. That's what's wrong. >> > > Fair enough. Assuming we kept "file-description locks" as a name, what > would you propose as new macro names? F_OFD_...? F_OPENFILE_...? If you said "file description" to me, I'd assume you made a typo. If, on the other hand, you said "open file" or "open file description" or, ugh, "struct file", I think I'd understand. --Andy