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: <84814064-9b38-5be5-37c9-987668d10a00@verizon.com>
Date:	Mon, 1 Aug 2016 11:37:31 -0400
From:	"Levin, Alexander" <alexander.levin@...izon.com>
To:	Guenter Roeck <linux@...ck-us.net>,
	"Levin, Alexander" <alexander.levin@...izon.com>
CC:	陈华才 <chenhc@...ote.com>,
	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 08/01/2016 11:29 AM, Guenter Roeck wrote:
> Hi Sasha,
> 
> On Mon, Aug 01, 2016 at 10:58:31AM -0400, Levin, Alexander wrote:
> [ ... ]
>>>
>>> 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.
>>
> 
> It would be great if you can also address the sparc64 problem
> I reported in my second e-mail.

Yup, I reverted that commit as well.

> Any chance you can add linux@...ck-us.net to your release candidate
> announcement e-mails ? This would help making sure that I don't miss
> a release.

I actually talked with Greg about it a while back and decided to stop
doing "release candidates" because I never ended up getting any reports
on those. I keep getting lots of feedback on the "Added to the x.y
stable kernel" mails so I rely on those for now.

I'll add that mail to the cover letter I send out when I do those, which
is essentially equivalent (and actually gives more time) if that sounds
ok to you.


Thanks,
Sasha