linux-kernel - Re: [PATCH 02/20] STAGING/lustre: limit follow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150419213348.GH889@ZenIV.linux.org.uk>
Date:	Sun, 19 Apr 2015 22:33:48 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Andreas Dilger <adilger@...ger.ca>
Cc:	NeilBrown <neilb@...e.de>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, Oleg Drokin <oleg.drokin@...el.com>,
	Andreas Dilger <andreas.dilger@...el.com>
Subject: Re: [PATCH 02/20] STAGING/lustre: limit follow_link recursion using
 stack space.

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 ;-/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/