linux-kernel - Re: [PATCH 7/8] tracing: Show module names and addresses of last boot

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: <20250206210247.4daa94c8@gandalf.local.home>
Date: Thu, 6 Feb 2025 21:02:47 -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 7/8] tracing: Show module names and addresses of last
 boot

On Fri, 7 Feb 2025 10:51:11 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:

> >   # cat instances/boot_mapped/last_boot_info
> >   Offset: 10c00000
> >   ffffffffc00ca000 usb_serial_simple
> >   ffffffffc00ae000 usbserial
> >   ffffffffc008b000 bfq  
> 
> This is just a suggestion, what about using the same format for all
> lines? For example,
> 
> # cat instances/boot_mapped/last_boot_info
> 10c00000         [kernel]
> ffffffffc00ca000 usb_serial_simple
> ffffffffc00ae000 usbserial
> ffffffffc008b000 bfq

This can be confusing because the first is an offset, and the others are
addresses.

> 
> > 
> >   # echo function > instances/boot_mapped/current_tracer
> >   # cat instances/boot_mapped/last_boot_info
> >   Offset: current  
> 
> And this one is empty if it is already for the current.
> (because last boot information is cleared)

Hmm, I have to think about that.

Thanks,

-- Steve