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  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]
Date:   Wed, 6 Mar 2019 05:20:56 +0000
From:   Rui Zhao <>
To:     James Morse <>
CC:     Sasha Levin <>, "" <>,
        "" <>,
        "" <>,
        "" <>,
        Linux Kernel <>,
        "" <>,
        "" <>
Subject: RE: [PATCH] EDAC, dmc520:: add DMC520 EDAC driver

Hi James,

> On Tuesday, February 5, 2019 9:31 AM, James Morse wrote:

>> We have firmware to config the memory controller and want to have an EDAC driver to report ECC status.

>> Could you please elaborate a bit on the security concern on this 
>> approach? Like some malicious app/driver can access memory controller registers can cause issue?

> I'm remembering this:

> Robin Murphy wrote:
> | [ For anyone interested, it puts the DRAM controller into sleep mode.
> | The kernel can't even panic if all the memory suddenly disappears :D ]

> This would be a problem if you need your Secure-world software needs to keep working, and depends on the memory behind this controller.

> It might be that your secure-world software only uses some other memory, in which case this wouldn't matter.
> It may be linux _is_ your secure-world software, in which case it wouldn't matter either.

We had internal discussion with our security team and in our product we do trust Linux. I'll send an updated patch to move platform specific settings like interrupt config to DT and include DT bindings doc for this driver.


Powered by blists - more mailing lists