From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935001AbcA1IRN (ORCPT ); Thu, 28 Jan 2016 03:17:13 -0500 Received: from mail-io0-f170.google.com ([209.85.223.170]:33719 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934977AbcA1IRL (ORCPT ); Thu, 28 Jan 2016 03:17:11 -0500 MIME-Version: 1.0 In-Reply-To: <56A9797E.6030600@roeck-us.net> References: <20160127180805.624425994@linuxfoundation.org> <56A9797E.6030600@roeck-us.net> Date: Thu, 28 Jan 2016 09:17:10 +0100 Message-ID: Subject: Re: [PATCH 4.1 000/127] 4.1.17-stable review From: Ard Biesheuvel To: Guenter Roeck Cc: Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , Linus Torvalds , Andrew Morton , shuah.kh@samsung.com, info@kernelci.org, "stable@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28 January 2016 at 03:14, Guenter Roeck 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.