linux-kernel - Re: [PATCH] page flags: prioritize kasan bits over last-cpuid

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-next>] [day] [month] [year] [list]

Message-ID: <20190805165128.GA23762@roeck-us.net>
Date:   Mon, 5 Aug 2019 09:51:28 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] page flags: prioritize kasan bits over last-cpuid

On Fri, Aug 02, 2019 at 09:49:02PM -0700, Arnd Bergmann wrote:
> ARM64 randdconfig builds regularly run into a build error, especially
> when NUMA_BALANCING and SPARSEMEM are enabled but not SPARSEMEM_VMEMMAP:
> 
>   #error "KASAN: not enough bits in page flags for tag"
> 
> The last-cpuid bits are already contitional on the available space, so
> the result of the calculation is a bit random on whether they were
> already left out or not.
> 
> Adding the kasan tag bits before last-cpuid makes it much more likely to
> end up with a successful build here, and should be reliable for
> randconfig at least, as long as that does not randomize NR_CPUS or
> NODES_SHIFT but uses the defaults.
> 
> In order for the modified check to not trigger in the x86 vdso32 code
> where all constants are wrong (building with -m32), enclose all the
> definitions with an #ifdef.
> 

This results in 

./include/linux/page-flags-layout.h:95:2: error: #error "Not enough bits in page flags"
 #error "Not enough bits in page flags"

when trying to build mipsel64:fuloong2e_defconfig.

Guenter