From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH -V4 2/6] vfs: Add name to file handle conversion support Date: Mon, 26 Apr 2010 05:52:08 -0400 Message-ID: <20100426095208.GA23020@infradead.org> References: <1272022715-11716-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> <1272022715-11716-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com> <6EE769C5-7307-49FF-BA8B-8C19EF04373E@sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Aneesh Kumar K.V" , hch@infradead.org, viro@zeniv.linux.org.uk, corbet@lwn.net, serue@us.ibm.com, linux-fsdevel@vger.kernel.org, sfrench@us.ibm.com To: Andreas Dilger Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:50545 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752301Ab0DZJwN (ORCPT ); Mon, 26 Apr 2010 05:52:13 -0400 Content-Disposition: inline In-Reply-To: <6EE769C5-7307-49FF-BA8B-8C19EF04373E@sun.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Apr 23, 2010 at 04:02:14PM -0600, Andreas Dilger wrote: > Out of curiosity, why not do this for other types of files? It makes sense from a consistency POV, so that the userspace code doesn't have to special-case each file by checking the type first (which would mean doing an extra path traversal and stat for each file first, adding overhead). This limitation seems to be copied from the original XFS handle code, but I don't see any good reason to stay with it.