linux-kernel - Re: Pstore : Query on using ramoops driver for DDR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9a653cf1-ab22-15c1-d021-a7cfe2b78276@codeaurora.org>
Date:   Wed, 10 Feb 2021 21:03:20 +0530
From:   Mukesh Ojha <mojha@...eaurora.org>
To:     "Luck, Tony" <tony.luck@...el.com>,
        lkml <linux-kernel@...r.kernel.org>
Cc:     "keescook@...omium.org" <keescook@...omium.org>,
        Anton Vorontsov <anton@...msg.org>,
        "ccross@...roid.com" <ccross@...roid.com>
Subject: Re: Pstore : Query on using ramoops driver for DDR


On 2/10/2021 2:32 AM, Luck, Tony wrote:
>> Can we use existing backend pstore ram driver (fs/pstore/ram.c) for DDR
>> instead of SRAM ?
> The expectation for pstore is that the system will go through a reset when it
> crashes. Most systems do not preserve DDR contents across reset.
>
> to support DDR, If we have a mechanism to copy stored data from DDR to
> external device after the crash.
>> Was the current driver written only to support persistant RAM like SRAM
>> or it can accept further change
> Linux is in a constant state of change :-)
>
> See above about DDR contents.   But if you have a platform that does preserve
> DDR contents until your "mechanism" can copy the pstore buffer, then post
> a patch.

Thanks for the reply

I have posted the patch.

https://lore.kernel.org/patchwork/patch/1378949/

-Mukesh


>

> -Tony