linux-kernel - Re: [PATCH 0/4] proc/kcore: performance optimizations

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: <20241112-lohnt-bestanden-d0a0ae380679@brauner>
Date: Tue, 12 Nov 2024 10:35:37 +0100
From: Christian Brauner <brauner@...nel.org>
To: Omar Sandoval <osandov@...ndov.com>
Cc: kernel-team@...com, linux-kernel@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH 0/4] proc/kcore: performance optimizations

On Mon, Nov 11, 2024 at 10:08:39AM -0800, Omar Sandoval wrote:
> On Mon, Nov 11, 2024 at 10:00:54AM +0100, Christian Brauner wrote:
> > On Fri, 08 Nov 2024 17:28:38 -0800, Omar Sandoval wrote:
> > > From: Omar Sandoval <osandov@...com>
> > > 
> > > Hi,
> > > 
> > > The performance of /proc/kcore reads has been showing up as a bottleneck
> > > for drgn. drgn scripts often spend ~25% of their time in the kernel
> > > reading from /proc/kcore.
> > > 
> > > [...]
> > 
> > A bit too late for v6.13, I think but certainly something we can look at
> > for v6.14. And great that your stepping up to maintain it!
> 
> Thanks, v6.14 is totally fine!
> 
> I have a quick question on logistics. /proc/kcore typically only gets a
> handful of patches per cycle, if any, so should we add fsdevel to the
> MAINTAINERS entry so I can ask you to queue up patches in the vfs tree
> once I've reviewed them? Or should I send pull requests somewhere?

You can do that as you please. I can just pick them up once you've acked
them. I'm happy to do that.