[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <166606025456.13363.3829702374064563472.stgit@donald.themaw.net>
Date: Tue, 18 Oct 2022 10:32:34 +0800
From: Ian Kent <raven@...maw.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Tejun Heo <tj@...nel.org>
Cc: Minchan Kim <minchan@...nel.org>,
Eric Sandeen <sandeen@...deen.net>,
Al Viro <viro@...IV.linux.org.uk>,
Rick Lindsley <ricklind@...ux.vnet.ibm.com>,
David Howells <dhowells@...hat.com>,
Miklos Szeredi <miklos@...redi.hu>,
Carlos Maiolino <cmaiolino@...hat.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] kernfs: remove i_lock usage that isn't needed
In the patch series to change the global kernfs mutex to a read-write
semaphore the inode i_lock is used in several functions.
But after thinking about it the i_lock is in fact not needed.
Signed-off-by: Ian Kent <raven@...maw.net>
---
Ian Kent (2):
kernfs: dont take i_lock on inode attr read
kernfs: dont take i_lock on revalidate
fs/kernfs/dir.c | 24 +++++++++++++++++-------
fs/kernfs/inode.c | 4 ----
2 files changed, 17 insertions(+), 11 deletions(-)
--
Ian
Powered by blists - more mailing lists