[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1536584468-15695-1-git-send-email-gaoxiang25@huawei.com>
Date: Mon, 10 Sep 2018 21:01:07 +0800
From: Gao Xiang <gaoxiang25@...wei.com>
To: "Theodore Y. Ts'o" <tytso@....edu>,
Jaegeuk Kim <jaegeuk@...nel.org>
CC: Eric Biggers <ebiggers@...gle.com>,
<linux-fscrypt@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Chao Yu <yuchao0@...wei.com>, Miao Xie <miaoxie@...wei.com>,
<weidu.du@...wei.com>, Gao Xiang <gaoxiang25@...wei.com>
Subject: [RFC PATCH 1/2] fscrypt: remove d_lock on reading DCACHE_ENCRYPTED_WITH_KEY
It seems there is no need to take d_lock when
accessing dentry->d_flags & DCACHE_ENCRYPTED_WITH_KEY
in fscrypt_d_revalidate. It only needs to be
serialized for updating.
Signed-off-by: Gao Xiang <gaoxiang25@...wei.com>
---
Hi,
At glance, I have no idea why fscrypt_d_revalidate disables
RCU-lookup. Therefore I made patches to raise a question and
do some basic test, and it seems to work.
Thanks,
fs/crypto/crypto.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
index 0f46cf5..b38c574 100644
--- a/fs/crypto/crypto.c
+++ b/fs/crypto/crypto.c
@@ -329,9 +329,8 @@ static int fscrypt_d_revalidate(struct dentry *dentry, unsigned int flags)
return 0;
}
- spin_lock(&dentry->d_lock);
- cached_with_key = dentry->d_flags & DCACHE_ENCRYPTED_WITH_KEY;
- spin_unlock(&dentry->d_lock);
+ cached_with_key = READ_ONCE(dentry->d_flags) &
+ DCACHE_ENCRYPTED_WITH_KEY;
dir_has_key = (d_inode(dir)->i_crypt_info != NULL);
dput(dir);
--
1.9.1
Powered by blists - more mailing lists