lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250415154413.15326-1-alexjlzheng@tencent.com>
Date: Tue, 15 Apr 2025 23:44:13 +0800
From: Jinliang Zheng <alexjlzheng@...il.com>
To: gregkh@...uxfoundation.org
Cc: alexjlzheng@...il.com,
	alexjlzheng@...cent.com,
	linux-kernel@...r.kernel.org,
	tj@...nel.org
Subject: Re: [PATCH kernfs 1/3] kernfs: switch global kernfs_idr_lock to per-fs lock

On Tue, 15 Apr 2025 17:16:46 +0200, gregkh@...uxfoundation.org wrote:
> On Mon, Apr 14, 2025 at 11:20:54AM +0800, Jinliang Zheng wrote:
> > > On Sat, Apr 12, 2025 at 07:50:54PM +0800, alexjlzheng@...il.com wrote:
> > > > On Sat, 12 Apr 2025 08:12:22 +0200, gregkh@...uxfoundation.org wrote:
> > > > > On Sat, Apr 13, 2025 at 02:31:07AM +0800, alexjlzheng@...il.com wrote:
> > > > > > From: Jinliang Zheng <alexjlzheng@...cent.com>
> > > > > > 
> > > > > > The kernfs implementation has big lock granularity(kernfs_idr_lock) so
> > > > > > every kernfs-based(e.g., sysfs, cgroup) fs are able to compete the lock.
> > > > > > 
> > > > > > This patch switches the global kernfs_idr_lock to per-fs lock, which
> > > > > > put the spinlock into kernfs_root.
> > > > > > 
> > > > > > Signed-off-by: Jinliang Zheng <alexjlzheng@...cent.com>
> > > > > > ---
> > > > > >  fs/kernfs/dir.c             | 14 +++++++-------
> > > > > >  fs/kernfs/kernfs-internal.h |  1 +
> > > > > >  2 files changed, 8 insertions(+), 7 deletions(-)
> > > > > 
> > > > > What kind of testing / benchmark did you do for this series that shows
> > > > > that this works, AND that this actually is measureable?  What workload
> > > > > are you doing that causes these changes to be needed?
> > > > 
> > > > Thank you for your reply. :)
> > > > 
> > > > We are trying to implement a kernfs-based filesystem that will have
> > > > multiple instances running at the same time, i.e., multiple kernfs_roots.
> > > 
> > > I don't think that kernfs is meant for that very well, what is that
> > > filesystem going to be for?
> > 
> > Thank you for your reply. :)
> > 
> > Similar to cgroupfs and sysfs, it is used to export the status and configurations
> > of some kernel variables in hierarchical modes of the kernel. The only difference
> > is that it may have many instances, that is, many kernfs_roots.
> 
> Let's see that filesystem first please before determining more, as you
> would be adding a new user/kernel api that we all need to argue about :)
> 
> Anyway, for the 2 patches that Tejun agrees with here, can you resend
> just them?

Fine. I have resent them at https://lore.kernel.org/all/20250415153659.14950-1-alexjlzheng@tencent.com/

thanks,
Jinliang Zheng. :)

> 
> thanks,
> 
> greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ