Re: [PATCH v2] Documentation/tracing: Mention that RESET_ATTACK_MITIGATION can clear memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Steven Rostedt <rostedt@xxxxxxxxxxx> writes:

> On Mon, 07 Oct 2024 11:06:06 -0600
> Jonathan Corbet <corbet@xxxxxxx> wrote:
>
>> Steven Rostedt <rostedt@xxxxxxxxxxx> 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




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux