From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 1/4] fs: Introduce path_component_lookup Date: Sun, 6 May 2007 12:14:12 +0100 Message-ID: <20070506111412.GC1211@infradead.org> References: <11784065741163-git-send-email-jsipek@cs.sunysb.edu> <11784065742752-git-send-email-jsipek@cs.sunysb.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, akpm@linux-foundation.org, viro@ftp.linux.org.uk, Trond.Myklebust@netapp.com, neilb@suse.de, mhalcrow@us.ibm.com To: Josef 'Jeff' Sipek Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:39647 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933606AbXEFLOR (ORCPT ); Sun, 6 May 2007 07:14:17 -0400 Content-Disposition: inline In-Reply-To: <11784065742752-git-send-email-jsipek@cs.sunysb.edu> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I wrote up the suggestion before my first morning tea yesterday and must admit that the name path_component_lookup is pretty stupid. We don't just look up a component but any relative path starting from the vfsmount/dentry pair. How about vfs_path_lookup instead because it mirrors various other vfs_ function that are dentry based? Also as a new exported symbol it should get a kerneldoc comment describing it. > + if (likely(retval == 0)) { > + if (unlikely(!audit_dummy_context() && nd && nd->dentry && > + nd->dentry->d_inode)) > + audit_inode(name, nd->dentry->d_inode); > + } This should get the same simplification I suggested for do_path_lookup.