linux-kernel - Re: [PATCH 10/13] powerpc: Define KMSAN metadata address ranges for vmalloc and ioremap

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <87ttoju86p.fsf@kernel.org>
Date: Fri, 15 Dec 2023 14:57:42 +0530
From: Aneesh Kumar K.V <aneesh.kumar@...nel.org>
To: Nicholas Miehlbradt <nicholas@...ux.ibm.com>, glider@...gle.com,
	elver@...gle.com, dvyukov@...gle.com, akpm@...ux-foundation.org,
	mpe@...erman.id.au, npiggin@...il.com, christophe.leroy@...roup.eu
Cc: linux-mm@...ck.org, kasan-dev@...glegroups.com, iii@...ux.ibm.com,
	linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	Nicholas Miehlbradt <nicholas@...ux.ibm.com>
Subject: Re: [PATCH 10/13] powerpc: Define KMSAN metadata address ranges for
 vmalloc and ioremap

Nicholas Miehlbradt <nicholas@...ux.ibm.com> writes:

> Splits the vmalloc region into four. The first quarter is the new
> vmalloc region, the second is used to store shadow metadata and the
> third is used to store origin metadata. The fourth quarter is unused.
>

Do we support KMSAN for both hash and radix? If hash is not supported
can we then using radix.h for these changes?

> Do the same for the ioremap region.
>
> Module data is stored in the vmalloc region so alias the modules
> metadata addresses to the respective vmalloc metadata addresses. Define
> MODULES_VADDR and MODULES_END to the start and end of the vmalloc
> region.
>
> Since MODULES_VADDR was previously only defined on ppc32 targets checks
> for if this macro is defined need to be updated to include
> defined(CONFIG_PPC32).

-aneesh