From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [git pull] vfs.git; pile 1 Date: Mon, 23 Jul 2012 10:03:04 +0100 Message-ID: <20120723090304.GF31729@ZenIV.linux.org.uk> References: <20120722100920.GZ31729@ZenIV.linux.org.uk> <20120722202030.GB31729@ZenIV.linux.org.uk> <500D0949.9040301@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Stephen Rothwell , Trond Myklebust To: Boaz Harrosh Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:52842 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750895Ab2GWJDJ (ORCPT ); Mon, 23 Jul 2012 05:03:09 -0400 Content-Disposition: inline In-Reply-To: <500D0949.9040301@panasas.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Jul 23, 2012 at 11:20:25AM +0300, Boaz Harrosh wrote: > On 07/22/2012 11:20 PM, Al Viro wrote: > > > I think the least painful solution is this: I've created a new branch > > (for-linus-2) in there, growing off the parent of merge in nfs.git. > > I've put the fixup to kern_path_locked() there as a separate commit > > + stuff that went in for-linus after that point. > > > > > Does this means that between "kern_path_locked() patch" and it's fixup > the tree is not bisectable? or is it just an enhancement/simplification? > > Not having any opinion, just wants to know It is bisectable, all right; lookup_one_len() is OK there (note that places converted to kern_path_locked() used to use it before the conversion. It's just that lookup_one_len() is an overkill - we have already checked exec permissions on parent and we'd already calculated the full qstr for last component - both length and hash. All that is left to do is actual __lookup_hash()...