From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Stefan (metze) Metzmacher" Subject: Re: [PATCH] locks: rename file-private locks to file-description locks Date: Mon, 21 Apr 2014 18:05:46 +0200 Message-ID: <535541DA.8040601@samba.org> References: <1398087935-14001-1-git-send-email-jlayton@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, samba-technical@lists.samba.org, Ganesha NFS List , Carlos O'Donell , libc-alpha , Michael Kerrisk To: Jeff Layton , linux-fsdevel@vger.kernel.org Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <1398087935-14001-1-git-send-email-jlayton@redhat.com> List-Id: linux-fsdevel.vger.kernel.org Am 21.04.2014 15:45, schrieb Jeff Layton: > File-private locks have been merged into Linux for v3.15, and *now* > people are commenting that the name and macro definitions for the new > file-private locks suck. > > ...and I can't even disagree. The names and command macros do suck. > > We're going to have to live with these for a long time, so it's > important that we be happy with the names before we're stuck with them. > > The consensus on the lists so far is that they should be rechristened as > "file-description locks". > > This patch makes the following changes that I think are necessary before > v3.15 ships: > > 1) rename the command macros to their new names. These end up in the uapi > headers and so are part of the external-facing API. It turns out that > glibc doesn't actually use the fcntl.h uapi header, but it's hard to > be sure that something else won't. Changing it now is safest. > > 2) make the the /proc/locks output display these as type "FDLOCK" > > The rest of the renaming can wait until v3.16, since everything else > isn't visible outside of the kernel. > > Cc: Michael Kerrisk > Signed-off-by: Jeff Layton Reviewed-by: Stefan Metzmacher