linux-kernel - Re: [PATCH 4/8] tracing: Have persistent trace instances save KASLR offset

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250206200316.1483aa59@gandalf.local.home>
Date: Thu, 6 Feb 2025 20:03:16 -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>
Subject: Re: [PATCH 4/8] tracing: Have persistent trace instances save KASLR
 offset

On Fri, 7 Feb 2025 09:58:44 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:

> > Which would make sure that the scratch size contains enough memory to hold
> > 128 modules.  
> 
> Yeah, this idea looks godd to me. BTW, the scratch size will be aligned to
> the subbuffer size (or page size?)

I don't think it needs to be. I think it just needs to be aligned to word
size.

-- Steve