Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933035AbbDUQq7 (ORCPT ); Tue, 21 Apr 2015 12:46:59 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:38041 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932584AbbDUQqw (ORCPT ); Tue, 21 Apr 2015 12:46:52 -0400 Message-ID: <55367EF8.5090304@plexistor.com> Date: Tue, 21 Apr 2015 19:46:48 +0300 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Al Viro , Richard Weinberger CC: Christoph Hellwig , Linus Torvalds , NeilBrown , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [RFC][PATCHSET] non-recursive link_path_walk() and reducing stack footprint References: <20150420181222.GK889@ZenIV.linux.org.uk> <20150421144959.GR889@ZenIV.linux.org.uk> <20150421150408.GA29838@infradead.org> <553668C1.8030707@nod.at> <20150421154504.GT889@ZenIV.linux.org.uk> In-Reply-To: <20150421154504.GT889@ZenIV.linux.org.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 22 On 04/21/2015 06:45 PM, Al Viro wrote: > On Tue, Apr 21, 2015 at 05:12:01PM +0200, Richard Weinberger wrote: > >> I'm pretty sure we can kill it. I had the plan to rip it out during this merge window >> along with other broken UML stuff but I was too late to ask on the UML mailinglist >> if someone is using it (which I really doubt). >> So, let's kill it with v4.2. > > Let's do it. Then ->put_link() is left in an interesting situation - *all* > instances only use the 'cookie' argument... A future user of inode or anything else can embed that in the cookie anyway. Just my $0.017 Boaz -- 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/