linux-kernel - Re: [PATCH v4 0/2] tracing: Make persistent ring buffer freeable

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: <20250225155532.0eb75041@gandalf.local.home>
Date: Tue, 25 Feb 2025 15:55:32 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Mark
 Rutland <mark.rutland@....com>, Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>, Andrew Morton
 <akpm@...ux-foundation.org>, Mike Rapoport <rppt@...nel.org>,
 linux-mm@...ck.org
Subject: Re: [PATCH v4 0/2] tracing: Make persistent ring buffer freeable

On Wed, 19 Feb 2025 00:08:47 +0900
"Masami Hiramatsu (Google)" <mhiramat@...nel.org> wrote:

> Hi,
> 
> Here is the 4th version of patches for making the persistent ring buffer
> freeable. The previous version is here;
> 
> https://lore.kernel.org/all/173928521419.906035.17750338150436695675.stgit@devnote2/
> 
> In this version, I used free_reserved_area() instead of custom releasing
> code. This seems working correctly. Thanks Mike!
> 

Thanks Masami,

I'll start testing this after the fixes I have get tested. I'm currently
testing the fixes for the sorttable linux-next fixes, after that I'm going
to test the histogram fix, and then I'll test these patches.

-- Steve