From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mike Rapoport <mike.rapoport@gmail.com>,
Kees Cook <keescook@chromium.org>,
Ard Biesheuvel <ardb@kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH v2] Documentation/tracing: Mention that RESET_ATTACK_MITIGATION can clear memory
Date: Mon, 07 Oct 2024 11:37:12 -0600 [thread overview]
Message-ID: <878quzizlj.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241007130858.7e25daeb@gandalf.local.home>
Steven Rostedt <rostedt@goodmis.org> writes:
> On Mon, 07 Oct 2024 11:06:06 -0600
> Jonathan Corbet <corbet@lwn.net> wrote:
>
>> Steven Rostedt <rostedt@goodmis.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.
*Grumble... :)
I haven't pushed out my tree yet, so I can replace the other one.
jon
prev parent reply other threads:[~2024-10-07 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 13:57 [PATCH v2] Documentation/tracing: Mention that RESET_ATTACK_MITIGATION can clear memory Steven Rostedt
2024-10-04 23:38 ` Steven Rostedt
2024-10-07 17:06 ` Jonathan Corbet
2024-10-07 17:08 ` Steven Rostedt
2024-10-07 17:37 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878quzizlj.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=ardb@kernel.org \
--cc=hdegoede@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mike.rapoport@gmail.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox