[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190417165556.GI4686@mit.edu>
Date: Wed, 17 Apr 2019 12:55:56 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-fscrypt@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH v2 2/2] fscrypt: cache decrypted symlink target in
->i_link
On Wed, Apr 10, 2019 at 01:21:15PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> Path lookups that traverse encrypted symlink(s) are very slow because
> each encrypted symlink needs to be decrypted each time it's followed.
> This also involves dropping out of rcu-walk mode.
>
> Make encrypted symlinks faster by caching the decrypted symlink target
> in ->i_link. The first call to fscrypt_get_symlink() sets it. Then,
> the existing VFS path lookup code uses the non-NULL ->i_link to take the
> fast path where ->get_link() isn't called, and lookups in rcu-walk mode
> remain in rcu-walk mode.
>
> Also set ->i_link immediately when a new encrypted symlink is created.
>
> To safely free the symlink target after an RCU grace period has elapsed,
> introduce a new function fscrypt_free_inode(), and make the relevant
> filesystems call it just before actually freeing the inode.
>
> Cc: Al Viro <viro@...iv.linux.org.uk>
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
Looks good, applied.
- Ted
Powered by blists - more mailing lists