On 28 January 2016 at 03:14, Guenter Roeck <linux@xxxxxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html