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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e28daeb8a1d74d60a3acb5c582f92123@intel.com>
Date:   Tue, 9 Feb 2021 21:02:57 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Mukesh Ojha <mojha@...eaurora.org>,
        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

> 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.

> 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 :-)

> to support DDR, If we have a mechanism to copy stored data from DDR to 
> external device after the crash.

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.

-Tony