[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241007130858.7e25daeb@gandalf.local.home>
Date: Mon, 7 Oct 2024 13:08:58 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jonathan Corbet <corbet@....net>
Cc: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
<linux-trace-kernel@...r.kernel.org>, linux-doc@...r.kernel.org, Masami
Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Mike Rapoport <mike.rapoport@...il.com>,
Kees Cook <keescook@...omium.org>, Ard Biesheuvel <ardb@...nel.org>, Hans
de Goede <hdegoede@...hat.com>
Subject: Re: [PATCH v2] Documentation/tracing: Mention that
RESET_ATTACK_MITIGATION can clear memory
On Mon, 07 Oct 2024 11:06:06 -0600
Jonathan Corbet <corbet@....net> wrote:
> Steven Rostedt <rostedt@...dmis.org> writes:
>
> > Jon,
> >
> > This version should be good to go.
>
> Applied, thanks.
And I now see I sent an older version that had a typo in it :-p
+ Note, saving the trace buffer across reboots does require that the system
+ is set up to not wipe memory. For instance, CONFIG_RESET_ATTACK_MITIGATION
+ can force a memory reset on boot which will clear any trace that was stored.
+ This is just one of many ways that can clear memory. Make sure you system
your system
+ keeps the content of memory across reboots before relying on this option.
+
I can send a v3.
-- Steve
Powered by blists - more mailing lists