linux-kernel - Re: [PATCH 1/3] ring-buffer: Add uname to match criteria for persistent ring buffer

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: <CAHk-=whV+=eymQ_eU8mj4fFw643nkvqZfeFM9gdGYavD44rB9w@mail.gmail.com>
Date: Tue, 17 Dec 2024 11:03:28 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, 
	Masami Hiramatsu <mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>, 
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Andrew Morton <akpm@...ux-foundation.org>, 
	stable@...r.kernel.org
Subject: Re: [PATCH 1/3] ring-buffer: Add uname to match criteria for
 persistent ring buffer

On Tue, 17 Dec 2024 at 10:42, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> My initial suggestion was to just fix up the boot time array.
>
> I think that's actually wrong. Just print the raw data and analyze it
> in user space.

.. I still think it's not the optimal solution, but fixing up the
event data from the previous boot (*before* printing it, and entirely
independently of vsnprintf()) would at least avoid the whole "mess
with vsnprintf and switch the format string around as you are trying
to walk the va_list in sync".

Because that was really a non-starter. Both the format string hackery
and the va_list hackery was just fundamentally bogus.

If you massage the data before printing - and independently of it -
those two issues should at least go away.

             Linus