From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 10 Apr 2019 01:33:46 +0100 From: Al Viro Subject: Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link Message-ID: <20190410003346.GT2217@ZenIV.linux.org.uk> References: <20190409233544.156665-1-ebiggers@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190409233544.156665-1-ebiggers@kernel.org> Sender: Al Viro To: Eric Biggers Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net List-ID: On Tue, Apr 09, 2019 at 04:35:44PM -0700, Eric Biggers wrote: > From: Eric Biggers > > Path lookups that traverse encrypted symlink(s) are very slow because > each encrypted symlink needs to be decrypted each time it's followed. > > Make encrypted symlinks faster by caching the decrypted symlink target > in ->i_link. The first call to ->get_link() sets it; later calls simply > return it. ->symlink() also sets it when the symlink is created. > > When the inode's ->i_crypt_info is freed, ->i_link is freed too. > > Note: RCU-delayed freeing of ->i_link is not yet implemented. > Therefore, for now even when ->i_link is set, path lookups must continue > to drop out of RCU-walk mode when following an encrypted symlink. And how the devil would they continue to do that, if I might ask? ->get_link() is *NOT* called if ->i_link is non-NULL, period.