linux-kernel - Re: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone

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 for Android: free password hash cracker in your pocket

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

Date:   Thu, 26 Oct 2017 14:50:05 +0100
From:   Will Deacon <will.deacon@....com>
To:     Neil Armstrong <narmstrong@...libre.com>
Cc:     khilman@...libre.com, carlo@...one.org,
        linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted
 Firmware reserved memory zone

On Wed, Oct 11, 2017 at 05:23:12PM +0200, Neil Armstrong wrote:
> This year, Amlogic updated the ARM Trusted Firmware reserved memory mapping
> for Meson GXL SoCs and products sold since May 2017 uses this alternate
> reserved memory mapping.
> But products had been sold using the previous mapping.
> 
> This issue has been explained in [1] and a dynamic solution is yet to be
> found to avoid loosing another 3Mbytes of reservable memory.
> 
> In the meantime, this patch adds this alternate memory zone only for
> the GXL and GXM SoCs since GXBB based new products stopped earlier.
> 
> [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/004860.html
> 
> Fixes: bba8e3f42736 ("ARM64: dts: meson-gx: Add firmware reserved memory zones")
> Reported-by: Jerome Brunet <jbrunet@...libre.com>
> Signed-off-by: Neil Armstrong <narmstrong@...libre.com>
> ---
>  arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 8 ++++++++
>  1 file changed, 8 insertions(+)

Thanks. Without this patch, memtest dies early on at physical address
0x05100000 due to an SError. With the patch, things work well, so:

Acked-by: Will Deacon <will.deacon@....com>
Tested-by: Will Deacon <will.deacon@....com>

Please also CC stable, because random SErrors under load aren't much fun ;)

Cheers,

Will