Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   fengyubo <fengyubo3@huawei.com>
To:     <hirofumi@mail.parknet.co.jp>
CC:     <fangwei1@huawei.com>, <fengyubo3@huawei.com>,
        <linux-kernel@vger.kernel.org>
Subject: [PATCH] fatfs: switch write_lock to read_lock in fat_ioctl_get_attributes
Date:   Sun, 28 Jun 2020 09:34:13 +0800
Message-ID: <1593308053-12702-1-git-send-email-fengyubo3@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Yubo Feng <fengyubo3@huawei.com>

There is no necessery to hold write_lock in fat_ioctl_get_attributes.
write_lock may make an impact on concurrency of fat_ioctl_get_attributes.

Signed-off-by: Yubo Feng <fengyubo3@huawei.com>
---
 fs/fat/file.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/fat/file.c b/fs/fat/file.c
index 42134c5..f9ee27c 100644
--- a/fs/fat/file.c
+++ b/fs/fat/file.c
@@ -25,9 +25,9 @@ static int fat_ioctl_get_attributes(struct inode *inode, u32 __user *user_attr)
 {
 	u32 attr;
 
-	inode_lock(inode);
+	inode_lock_shared(inode);
 	attr = fat_make_attrs(inode);
-	inode_unlock(inode);
+	inode_unlock_shared(inode);
 
 	return put_user(attr, user_attr);
 }
-- 
2.7.4