linux-kernel - mips/sparc64 build failures in v3.18.38 and v4.1.29

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

Date:	Sun, 31 Jul 2016 17:23:19 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Sasha Levin <alexander.levin@...izon.com>,
	stable <stable@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: mips/sparc64 build failures in v3.18.38 and v4.1.29

[ again, this time with Sasha's new e-mail address, and updated ]

Build failures in v3.18.38 and 4.1.29:

mips builds:

arch/mips/kernel/setup.c: In function 'arch_mem_init':
arch/mips/kernel/setup.c:689:2: error: implicit declaration of function 'reserve_bootmem_region'

Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for hibernation").
It fixes a bug which does not exist in 3.18 / 4.1, in turn causing all mips builds in 3.18
and 4.1 to fail.

sparc64 builds:

mm/init_64.c: In function 'bootmem_init_numa':
arch/sparc/mm/init_64.c:1311:4: error: 'numa_latency' undeclared

Caused by 0396a871c4e3 ("sparc64: Fix numa node distance initialization").
'numa_latency' does not exist in 3.18 and 4.1. It was introduced upstream with commit
52708d690b8be ("sparc64: Fix numa distance values").

Guenter