From: akpm@linux-foundation.org
To: fengyubo3@huawei.com, hirofumi@mail.parknet.co.jp,
mm-commits@vger.kernel.org
Subject: [merged] fatfs-switch-write_lock-to-read_lock-in-fat_ioctl_get_attributes.patch removed from -mm tree
Date: Wed, 12 Aug 2020 14:04:56 -0700 [thread overview]
Message-ID: <20200812210456.Uq59NG9EW%akpm@linux-foundation.org> (raw)
The patch titled
Subject: fatfs: switch write_lock to read_lock in fat_ioctl_get_attributes
has been removed from the -mm tree. Its filename was
fatfs-switch-write_lock-to-read_lock-in-fat_ioctl_get_attributes.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Yubo Feng <fengyubo3@huawei.com>
Subject: fatfs: switch write_lock to read_lock in fat_ioctl_get_attributes
There is no need to hold write_lock in fat_ioctl_get_attributes.
write_lock may make an impact on concurrency of fat_ioctl_get_attributes.
Link: http://lkml.kernel.org/r/1593308053-12702-1-git-send-email-fengyubo3@huawei.com
Signed-off-by: Yubo Feng <fengyubo3@huawei.com>
Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/fat/file.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/fs/fat/file.c~fatfs-switch-write_lock-to-read_lock-in-fat_ioctl_get_attributes
+++ a/fs/fat/file.c
@@ -25,9 +25,9 @@ static int fat_ioctl_get_attributes(stru
{
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);
}
_
Patches currently in -mm which might be from fengyubo3@huawei.com are
reply other threads:[~2020-08-12 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200812210456.Uq59NG9EW%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengyubo3@huawei.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
/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).