diff options
| author | Steven Rostedt <rostedt@goodmis.org> | 2024-10-07 13:16:53 -0400 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2024-10-14 09:50:30 -0600 |
| commit | f7e1d19105b20f23f2ffb6d4949bb2a20bd56da0 (patch) | |
| tree | 4721b7659e7b5585a9b5d337a370e80706f0c352 /scripts/lib/kdoc/kdoc_output.py | |
| parent | f3904bb70aab5e4067eed53869963a919b23a9d6 (diff) | |
Documentation/tracing: Mention that RESET_ATTACK_MITIGATION can clear memory
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>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20241007131653.35837081@gandalf.local.home
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions