From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@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>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/tracing: Mention that RESET_ATTACK_MITIGATION can clear memory
Date: Mon, 30 Sep 2024 11:20:48 -0600 [thread overview]
Message-ID: <87ikud9hxr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240930131415.1438c0b7@gandalf.local.home>
Steven Rostedt <rostedt@goodmis.org> writes:
> On Thu, 26 Sep 2024 19:54:48 +0200
> Hans de Goede <hdegoede@redhat.com> wrote:
>
>> Hi,
>>
>> On 26-Sep-24 7:01 PM, Steven Rostedt wrote:
>> > From: Steven Rostedt <rostedt@goodmis.org>
>> >
>> > At the 2024 Linux Plumbers Conference, I was talking with Hans de Goede
>> > about the persistent buffer to display traces from previous boots. He
>> > mentioned that UEFI can clear memory. In my own tests I have not seen
>> > this. He later informed me that it requires the config option:
>> >
>> > CONFIG_RESET_ATTACK_MITIGATION
>> >
>> > It appears that setting this will allow the memory to be cleared on boot
>> > up, which will definitely clear out the trace of the previous boot.
>> >
>> > Add this information under the trace_instance in kernel-parameters.txt
>> > to let people know that this can cause issues.
>> >
>> > Link: https://lore.kernel.org/all/20170825155019.6740-2-ard.biesheuvel@linaro.org/
>> >
>> > Reported-by: Hans de Goede <hdegoede@redhat.com>
>> > Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
>>
>> Thanks, patch looks good to me:
>>
>> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
> Thanks,
>
> And I forgot to send this to the Documentation maintainers :-p
>
> Jon, could you take this? Do you need me to resend, or can you just pull it
> from lore?
I'll grab it in a bit.
jon
next prev parent reply other threads:[~2024-09-30 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 17:01 Steven Rostedt
2024-09-26 17:54 ` Hans de Goede
2024-09-30 17:14 ` Steven Rostedt
2024-09-30 17:20 ` Jonathan Corbet [this message]
2024-09-30 17:24 ` Steven Rostedt
2024-10-01 6:17 ` Ard Biesheuvel
2024-10-01 8:56 ` Hans de Goede
2024-10-01 9:35 ` Ard Biesheuvel
2024-10-01 12:53 ` Steven Rostedt
2024-10-01 13:32 ` Ard Biesheuvel
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=87ikud9hxr.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
all inboxes | Powered by JetHome®