[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190728150927.GD6088@mit.edu>
Date: Sun, 28 Jul 2019 11:09:27 -0400
From: "Theodore Y. 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, linux-api@...r.kernel.org,
linux-crypto@...r.kernel.org, keyrings@...r.kernel.org,
Paul Crowley <paulcrowley@...gle.com>,
Satya Tangirala <satyat@...gle.com>
Subject: Re: [PATCH v7 04/16] fscrypt: add ->ci_inode to fscrypt_info
On Fri, Jul 26, 2019 at 03:41:29PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> Add an inode back-pointer to 'struct fscrypt_info', such that
> inode->i_crypt_info->ci_inode == inode.
>
> This will be useful for:
>
> 1. Evicting the inodes when a fscrypt key is removed, since we'll track
> the inodes using a given key by linking their fscrypt_infos together,
> rather than the inodes directly. This avoids bloating 'struct inode'
> with a new list_head.
>
> 2. Simplifying the per-file key setup, since the inode pointer won't
> have to be passed around everywhere just in case something goes wrong
> and it's needed for fscrypt_warn().
>
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
Looks good, feel free to add:
Reviewed-by: Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists