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
| ||
|
Date: Tue, 9 Aug 2022 09:41:28 -0700 From: Evgenii Stepanov <eugenis@...gle.com> To: Marc Zyngier <maz@...nel.org> Cc: Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Peter Collingbourne <pcc@...gle.com>, Vincenzo Frascino <vincenzo.frascino@....com>, Andrey Konovalov <andreyknvl@...il.com>, Mark Brown <broonie@...nel.org>, Linux ARM <linux-arm-kernel@...ts.infradead.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] mte: Follow arm64.nomte override in MMU setup. On Tue, Aug 9, 2022 at 1:50 AM Marc Zyngier <maz@...nel.org> wrote: > How comes such memory is being used? How comes it is in the linear > map? > > arm64.nomte is affecting the use of MTE feature on the platform. It > doesn't guard the use of a MTE carve-out, and doesn't allow it to be > used in any shape or form. > > To use this memory, you should remove the MTE configuration > altogether, as you cannot infer what the CPU is doing with it. This can be used to enable MTE in TZ but not in the NS memory.
Powered by blists - more mailing lists