From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [RFC] next cycle fun: ->release() API change Date: Sat, 11 May 2013 12:16:22 -0700 Message-ID: References: <20130509050343.GD25399@ZenIV.linux.org.uk> <20130511172242.GP25399@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: linux-fsdevel , Linux Kernel Mailing List To: Al Viro Return-path: Received: from mail-vb0-f44.google.com ([209.85.212.44]:59995 "EHLO mail-vb0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753004Ab3EKTQX (ORCPT ); Sat, 11 May 2013 15:16:23 -0400 In-Reply-To: <20130511172242.GP25399@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, May 11, 2013 at 10:22 AM, Al Viro wrote: >> >> Because renaming really doesn't buy us anything but pain. > > Umm... I'd rather go the whole way and get rid of inode argument as well, > while we are at it. It's completely redundant and it's unused in very large > majority of the instances. So? What's the advantage of removing it? Also, "->close()" would be *exactly* the wrong name to call this, since it would be absolutely and utterly misleading. "->release()" is _not_ about close, and in fact the whole return code is partially due to people thinking it is. It's "->flush()" that gets called at close time. Linus