From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 02/20] STAGING/lustre: limit follow_link recursion using stack space. Date: Sun, 19 Apr 2015 22:33:48 +0100 Message-ID: <20150419213348.GH889@ZenIV.linux.org.uk> References: <20150323023258.8161.32467.stgit@notabene.brown> <20150323023738.8161.97062.stgit@notabene.brown> <20150418030128.GF889@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: NeilBrown , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Oleg Drokin , Andreas Dilger To: Andreas Dilger Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:55467 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752387AbbDSVdy (ORCPT ); Sun, 19 Apr 2015 17:33:54 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Apr 19, 2015 at 02:57:07PM -0600, Andreas Dilger wrote: > I'd be happy if symlink recursion was removed completely, but so far the > added symlink recursion limit hasn't been a problem for Lustre users. Well, it's gone in my tree; I've just pushed the current queue to vfs.git#link_path_walk. Right now I'm looking at the unholy mess gcc does to stack footprint with inlining - the last commit in there is a result of exactly that. Inlines in there really need tuning ;-/