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
| ||
|
Message-ID: <CAB1t1CwzUCEL1josABxfyqX91Z6DsrbEuopsDYsgq-eNxh6Btw@mail.gmail.com> Date: Mon, 30 Jan 2023 15:19:03 +0100 From: Petr Vorel <petr.vorel@...il.com> To: Jamie Douglass <jamiemdouglass@...il.com> Cc: Andy Gross <agross@...nel.org>, Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org, Dominik Kobinski <dominikkobinski314@...il.com>, Konrad Dybico <konrad.dybico@...aro.org> Subject: Re: [PATCH] arm64: dts: qcom: msm8992-lg-bullhead: Correct memory overlap with SMEM region Hi Jamie, On Sat, 28 Jan 2023 at 06:53, Jamie Douglass <jamiemdouglass@...il.com> wrote: > > A previously committed reserved memory region was overlapping with the IMHO there should be marked commit which you're fixing: Fixes: 22c7e1a0fa45 ("arm64: dts: msm8992-bullhead: add memory hole region") > SMEM memory region, causing an error message in dmesg: > OF: reserved mem: OVERLAP DETECTED! > reserved@...0000 (0x0000000005000000--0x0000000007200000) > overlaps with smem_region@...0000 > (0x0000000006a00000--0x0000000006c00000) > This patch splits the previous reserved memory region into two > reserved sections either side of the SMEM memory region. Reviewed-by: Petr Vorel <pvorel@...e.cz> Tested-by: Petr Vorel <pvorel@...e.cz> ... > +++ b/arch/arm64/boot/dts/qcom/msm8992-lg-bullhead.dtsi > @@ -53,8 +53,13 @@ cont_splash_mem: memory@...0000 { > no-map; > }; > > - removed_region: reserved@...0000 { > - reg = <0 0x05000000 0 0x2200000>; > + reserved@...0000 { Can we keep "removed_region:" ? removed_region: reserved@...0000 { > + reg = <0x0 0x05000000 0x0 0x1a00000>; > + no-map; > + }; > + > + reserved@...0000 { Not sure which label to add, maybe append 2? removed_region2: reserved@...0000 { @Konrad @Krzysztof WDYT? Kind regards, Petr > + reg = <0x0 0x06c00000 0x0 0x400000>; > no-map; > }; > };
Powered by blists - more mailing lists