From: Eric Biggers <ebiggers@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Satya Tangirala <satyat@google.com>,
linux-api@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Paul Crowley <paulcrowley@google.com>
Subject: Re: [PATCH v4 07/17] fs/dcache.c: add shrink_dcache_inode()
Date: Wed, 3 Apr 2019 13:36:51 -0700 [thread overview]
Message-ID: <20190403203650.GA216239@gmail.com> (raw)
In-Reply-To: <20190403183411.GV2217@ZenIV.linux.org.uk>
On Wed, Apr 03, 2019 at 07:34:12PM +0100, Al Viro wrote:
> On Tue, Apr 02, 2019 at 08:45:50AM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > When a filesystem encryption key is removed, we need all files which had
> > been "unlocked" (had ->i_crypt_info set up) with it to appear "locked"
> > again. This is most easily done by evicting the inodes. This can
> > currently be done using 'echo 2 > /proc/sys/vm/drop_caches'; however,
> > that is overkill and not usable by non-root users.
> >
> > To evict just the needed inodes we also need the ability to evict those
> > inodes' dentries, since an inode is pinned by its dentries. Therefore,
> > add a function shrink_dcache_inode() which iterates through an inode's
> > dentries and evicts any unused ones as well as any unused descendants
> > (since there may be negative dentries pinning the inode's dentries).
>
> Huh?
>
> > + * Evict all unused aliases of the specified inode from the dcache. This is
> > + * intended to be used when trying to evict a specific inode, since inodes are
> > + * pinned by their dentries. We also have to descend to ->d_subdirs for each
> > + * alias, since aliases may be pinned by negative child dentries.
> > + */
> > +void shrink_dcache_inode(struct inode *inode)
> > +{
> > + for (;;) {
> > + struct select_data data;
> > + struct dentry *dentry;
> > +
> > + INIT_LIST_HEAD(&data.dispose);
> > + data.start = NULL;
> > + data.found = 0;
> > +
> > + spin_lock(&inode->i_lock);
> > + hlist_for_each_entry(dentry, &inode->i_dentry, d_u.d_alias)
> > + d_walk(dentry, &data, select_collect);
> > + spin_unlock(&inode->i_lock);
> > +
> > + if (!data.found)
> > + break;
> > +
> > + shrink_dentry_list(&data.dispose);
> > + cond_resched();
>
> This is... odd. What's wrong with
> if (S_ISDIR(inode->i_mode)) {
> dentry = d_find_any_alias(inode);
> if (dentry) {
> shrink_dcache_parent(dentry);
> dput(dentry);
> }
> }
> d_prune_aliases(inode);
> instead of that thing?
That works, as far as I can tell, so I'll do that instead.
I don't think I noticed that d_prune_aliases() existed when I wrote this.
Thanks for the suggestion!
- Eric
next prev parent reply other threads:[~2019-04-03 20:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 15:45 [PATCH v4 00/17] fscrypt: key management improvements Eric Biggers
2019-04-02 15:45 ` [PATCH v4 01/17] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h> Eric Biggers
2019-04-02 15:45 ` [PATCH v4 02/17] fscrypt: use FSCRYPT_ prefix for uapi constants Eric Biggers
2019-04-02 15:45 ` [PATCH v4 03/17] fscrypt: use FSCRYPT_* definitions, not FS_* Eric Biggers
2019-04-02 15:45 ` [PATCH v4 04/17] fscrypt: add ->ci_inode to fscrypt_info Eric Biggers
2019-04-02 15:45 ` [PATCH v4 05/17] fscrypt: refactor v1 policy key setup into keysetup_legacy.c Eric Biggers
2019-04-02 15:45 ` [PATCH v4 06/17] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl Eric Biggers
2019-04-02 15:45 ` [PATCH v4 07/17] fs/dcache.c: add shrink_dcache_inode() Eric Biggers
2019-04-03 18:34 ` Al Viro
2019-04-03 20:36 ` Eric Biggers [this message]
2019-04-02 15:45 ` [PATCH v4 08/17] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl Eric Biggers
2019-04-02 15:45 ` [PATCH v4 09/17] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl Eric Biggers
2019-04-02 15:45 ` [PATCH v4 10/17] fscrypt: add an HKDF-SHA512 implementation Eric Biggers
2019-04-02 15:45 ` [PATCH v4 11/17] fscrypt: v2 encryption policy support Eric Biggers
2019-04-02 15:45 ` [PATCH v4 12/17] fscrypt: allow unprivileged users to add/remove keys for v2 policies Eric Biggers
2019-04-02 15:45 ` [PATCH v4 13/17] fscrypt: require that key be added when setting a v2 encryption policy Eric Biggers
2019-04-02 15:45 ` [PATCH v4 14/17] ext4: wire up new fscrypt ioctls Eric Biggers
2019-04-02 15:45 ` [PATCH v4 15/17] f2fs: " Eric Biggers
2019-04-02 15:45 ` [PATCH v4 16/17] ubifs: " Eric Biggers
2019-04-02 15:46 ` [PATCH v4 17/17] fscrypt: document the new ioctls and policy version Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190403203650.GA216239@gmail.com \
--to=ebiggers@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=paulcrowley@google.com \
--cc=satyat@google.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).