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: <fd879d4e-13d7-bb82-8668-a1423fc7e428@linaro.org> Date: Mon, 30 Jan 2023 15:21:16 +0100 From: Konrad Dybcio <konrad.dybcio@...aro.org> To: Petr Vorel <petr.vorel@...il.com>, Jamie Douglass <jamiemdouglass@...il.com> Cc: Andy Gross <agross@...nel.org>, Bjorn Andersson <andersson@...nel.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 On 30.01.2023 15:19, Petr Vorel wrote: > 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") Yes > >> 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? Generally, if you don't expect that there'll be a need to amend/reference the node from somewhere else, the label is rather useless.. Konrad > > Kind regards, > Petr > >> + reg = <0x0 0x06c00000 0x0 0x400000>; >> no-map; >> }; >> };
Powered by blists - more mailing lists