linux-kernel - Re:mips builds failing 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <d702eb0e-d2d8-6e65-46b3-f10f18b7576d@verizon.com>
Date:	Mon, 1 Aug 2016 10:58:31 -0400
From:	"Levin, Alexander" <alexander.levin@...izon.com>
To:	陈华才 <chenhc@...ote.com>,
	Guenter Roeck <linux@...ck-us.net>,
	"Levin, Alexander" <alexander.levin@...izon.com>
CC:	stable <stable@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re:mips builds failing in v3.18.38 and v4.1.29

On 07/31/2016 09:56 PM, 陈华才 wrote:
> Hi,
> 
> I have already told Sasha that "MIPS: Reserve nosave data for hibernation" should not be backported to 4.1/3.18. But he has no response.
> 
> Huacai
>  
> ------------------ Original ------------------
> From:  "Guenter Roeck"<linux@...ck-us.net>;
> Date:  Mon, Aug 1, 2016 07:57 AM
> To:  "Sasha Levin"<sasha.levin@...cle.com>;
> Cc:  "stable"<stable@...r.kernel.org>; "linux-kernel@...r.kernel.org"<linux-kernel@...r.kernel.org>; "Huacai Chen"<chenhc@...ote.com>;
> Subject:  mips builds failing in v3.18.38 and v4.1.29
>  
> Sorry I didn't notice earlier - my 3.18/4.1 build scripts were broken.
> 
> 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.
> 
> Guenter
> 

I'm sorry, it mush have gotten lost in the email switch. I'll revert
that commit for the next stable release and hurry that up.


Thanks,
Sasha