linux-kernel - Re: [PATCH] mmap: Remove unused events vma_mas_szero and vma

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250605165650.7b0270a1@gandalf.local.home>
Date: Thu, 5 Jun 2025 16:56:50 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
 <linux-trace-kernel@...r.kernel.org>, linux-mm@...ck.org, Masami Hiramatsu
 <mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
 "Liam R. Howlett" <Liam.Howlett@...cle.com>, Lorenzo Stoakes
 <lorenzo.stoakes@...cle.com>, Vlastimil Babka <vbabka@...e.cz>, Jann Horn
 <jannh@...gle.com>
Subject: Re: [PATCH] mmap: Remove unused events vma_mas_szero and vma_store

On Thu, 5 Jun 2025 13:49:10 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Thu, 5 Jun 2025 16:19:59 -0400 Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > When the __vma_adjust() was converted to use the vma iterator it removed
> > the functions vma_mas_store() and vma_mas_remove(). These functions called
> > the tracepoints trace_vma_mas_store() and trace_vma_mas_szero()
> > respectively. The calls to these tracepoints were removed but the trace
> > events that created the tracepoints were not removed. Each trace event can
> > take up to 5K of memory, and it is allocated regardless of if they are
> > called or not.  
> 
> Thanks.  mm.git has an identical patch from Caleb Mateos
> (https://lkml.kernel.org/r/20250411161746.1043239-1-csander@purestorage.com)

Bah, that's why I didn't send it out. I just noticed it in my queue. I
forgot to delete it.

I even replied that I was going to send this and found out that it's the
patch that started everything.

Feel free to ignore. Sorry for the noise ;-)

-- Steve