linux-kernel - Re: [PATCH 4.1 000/127] 4.1.17-stable review

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: <CAKv+Gu8b-0+Zkv4hYfY3cqBBv7RhGHOiD=8XnYa3oqSUrkZpQA@mail.gmail.com>
Date:	Thu, 28 Jan 2016 09:17:10 +0100
From:	Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	shuah.kh@...sung.com, info@...nelci.org,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH 4.1 000/127] 4.1.17-stable review

On 28 January 2016 at 03:14, Guenter Roeck <linux@...ck-us.net> wrote:
> On 01/27/2016 10:12 AM, Greg Kroah-Hartman wrote:
>>
>> -------------------------
>> NOTE:
>>    There are still a lot of pending stable patches in the queue, well
>>    over 400 of them to be specific, so some of your favorite/pet patches
>>    might not be included in these releases.  Please be patient as I dig
>>    out from this backlog over the next few weeks.  If there are specific
>>    patches that you just _must_ have included in a stable release soon,
>>    please let me know.
>> -------------------------
>>
>> This is the start of the stable review cycle for the 4.1.17 release.
>> There are 127 patches in this series, all will be posted as a response
>> to this one.  If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Fri Jan 29 18:07:17 UTC 2016.
>> Anything received after that time might be too late.
>>
>
> Build results:
>         total: 139 pass: 138 fail: 1
> Failed builds:
>         arm64:allmodconfig
>
> Qemu test results:
>         total: 95 pass: 93 fail: 2
> Failed tests:
>         arm64:smp:defconfig
>         arm64:nosmp:defconfig
>
> arm64:allmodconfig fails to build due to a crash in recordmcount, which
> is caused by 'recordmcount: arm64: Replace the ignored mcount call into
> nop'.
> That bug can be fixed by applying upstream commit c84da8b9ad37
> ("recordmcount:
> Fix endianness handling bug for nop_mcount"). However, that does not help,
> because after applying this patch the build is then still broken due to
> 'arm64: mm: use correct mapping granularity under DEBUG_RODAT'.
>

Apologies for not spotting that when the patches were sent out for
stable review.
'arm64: mm: use correct mapping granularity under DEBUG_RODAT' needs a
special version for -stable which #defines SWAPPER_BLOCK_SIZE, since
that is a recent invention.

I will follow up with a new patch, please disregard this version in
the mean time

Thanks,
Ard.