Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965274AbbDVGky (ORCPT ); Wed, 22 Apr 2015 02:40:54 -0400 Received: from mga01.intel.com ([192.55.52.88]:44385 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964847AbbDVGkv convert rfc822-to-8bit (ORCPT ); Wed, 22 Apr 2015 02:40:51 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,622,1422950400"; d="scan'208";a="698983359" From: "Drokin, Oleg" To: Greg Kroah-Hartman CC: Christoph Hellwig , Boqun Feng , "" , "Dilger, Andreas" , "" , Al Viro , "" , Jan Kara Subject: Re: [PATCH 1/2] vfs: export symbol 'getname' and 'putname' Thread-Topic: [PATCH 1/2] vfs: export symbol 'getname' and 'putname' Thread-Index: AQHQfK+QTxCXxEubcUGDCCSFZfh7bZ1Y/TSAgAAKtQCAAAKdAA== Date: Wed, 22 Apr 2015 06:40:48 +0000 Message-ID: References: <1429674624-25922-1-git-send-email-boqun.feng@gmail.com> <1429674624-25922-2-git-send-email-boqun.feng@gmail.com> <20150422055311.GB3731@infradead.org> <20150422063130.GC24738@kroah.com> In-Reply-To: <20150422063130.GC24738@kroah.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.201.178] Content-Type: text/plain; charset="us-ascii" Content-ID: <72F5E85CD6ABC74C839DC93BCBFE9E82@intel.com> Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1728 Lines: 38 On Apr 22, 2015, at 2:31 AM, Greg Kroah-Hartman wrote: > On Tue, Apr 21, 2015 at 10:53:11PM -0700, Christoph Hellwig wrote: >> Nak on exporting symbols for broken staging code. Please get rid of >> the ioctls looking up path names in horrible ways in the lustre code. > > I agree with Christoph, we shouldn't be doing this. Let's fix lustre > "properly", which should be possible, right? Well, sort of. For the first ioctl we clearly can do an fd pass and get info from there (need to also teach the tools about the new ioctl, so I cannot submit a patch right away, but I'll get on it). In the second case the usecase is a bit more involved. It deals with the problem of having directory entry pointing to a non-existing directory (so basically a name only, but we do know it's supposed to be a directory, just on another server), so I doubt we can even open it to get the fd. Now, perhaps we can just allow regular rmdir to ignore the error and kill the bogus entry anyway, but there was this thought that we might want to alert the user there's something more fundamentally broken going on here, and so they would need to call this certain ioctl called if they just would like to kill the entry anyway as opposed to calling say fsck to make sure there's nothing else broken. I am not entirely sure of this idea myself, but it probably made sense at some point. I see there's quite a dislike for this approach, so we can remove it if there's no better option. Bye, Oleg-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/