From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1FA69C432C3 for ; Thu, 28 Nov 2019 05:02:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E6B7B215F1 for ; Thu, 28 Nov 2019 05:02:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="sOAAZbEJ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726467AbfK1FCX (ORCPT ); Thu, 28 Nov 2019 00:02:23 -0500 Received: from mail-lj1-f195.google.com ([209.85.208.195]:46585 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725789AbfK1FCX (ORCPT ); Thu, 28 Nov 2019 00:02:23 -0500 Received: by mail-lj1-f195.google.com with SMTP id e9so26949354ljp.13 for ; Wed, 27 Nov 2019 21:02:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wwAHZEA0jlGAecazH8A4WVcg6j9/yx6Hh8ujY0Dq/vM=; b=sOAAZbEJsiX980a7JeUj7a7cXAEr95sXDfUkO68+lZPsnHBdRXXUMmOuOUfkelWFY2 QXoGEOyxhVnNrKMCoI3Tg9MScml5yHLRbnXGUv7lilIRxSr3hqJ6afgvUC/KvDc3zVNA PC5oR2+SpOGiF0REPK275GWQmDzzoYNk9GY4s5bz+LiZQLnVZTJpqkyxEvaZ7mfqZxrI s+Wp3uvquKzzVBx4Lk5/vCmmlcE1VbRPMzLQ5kC38Jvzqoua5B7RRJexxunvid6APAIE Qhg3mYe0ytbf+Ncj3d3oYF45GdwObSSUrO3Iv5HTtHUjFQdrfXcs3FnGJN+1HmMfJZoG YJ5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wwAHZEA0jlGAecazH8A4WVcg6j9/yx6Hh8ujY0Dq/vM=; b=laqoqn1F8qq35gS0B+uzqSw7EpfyXH1pVGjPQ1a7kSDIbojCWlGWsXvsBMCYBMAM2J hRdo6BMceHABLV4Ptw5k7g4hW8Sq0vYDvzpr1OMyIN5pdZp3WAJiUvgVQyyKF8hXZb5G V6Y2YLn1NKP2dcCm8cFUqdUC4pxMvv6jN2f3skJWkenedS230egTg6zW2NtRPBLOYppH 00DX6MkiqU8b14YxVwdhHward53w0GMYO+Tl9quheeWLTpYAV1gnLQu4A3gmD4XTT9zq yFO0miZWYTWKZQVhusri/BB35Wdm6TgiXRUewZxkgCjL0UW1scQnOiXCnLFYTwWci3bs Mjyw== X-Gm-Message-State: APjAAAWYWjnZiI1bUhBWcWXMrTzcwKc1hXRLbjJT/kZTkQsbGAXVR/71 jT1hFAvmSmJHuJpAzfb/kh3S4o3eTe42CI3sp+hiShbLWxk= X-Google-Smtp-Source: APXvYqypJIEfugB0UvdI6BgmE5R9HF/glAtn2wZ4w1z6KcQ3egurLdE1sd9MVMGYQzf/dnSD7MS/1JAMuJmSR4Kq+w0= X-Received: by 2002:a2e:7202:: with SMTP id n2mr29808167ljc.194.1574917341238; Wed, 27 Nov 2019 21:02:21 -0800 (PST) MIME-Version: 1.0 References: <20191127203049.431810767@linuxfoundation.org> In-Reply-To: <20191127203049.431810767@linuxfoundation.org> From: Naresh Kamboju Date: Thu, 28 Nov 2019 10:32:10 +0530 Message-ID: Subject: Re: [PATCH 4.14 000/211] 4.14.157-stable review To: Greg Kroah-Hartman Cc: open list , Linus Torvalds , Andrew Morton , Guenter Roeck , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, linux- stable Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 28 Nov 2019 at 02:16, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.157 release. > There are 211 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, 29 Nov 2019 20:18:09 +0000. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.157-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h > This patch causing build failure for x86 32bit on stable-rc 4.14 and stable-rc-4.19 > Thomas Gleixner > x86/cpu_entry_area: Add guard page for entry stack on 32bit In file included from include/linux/kernel.h:10:0, from include/linux/list.h:9, from include/linux/preempt.h:11, from include/linux/spinlock.h:51, from arch/x86/mm/cpu_entry_area.c:3: In function 'setup_cpu_entry_area_ptes', inlined from 'setup_cpu_entry_areas' at arch/x86/mm/cpu_entry_area.c:164:2: include/linux/compiler.h:334:38: error: call to '__compiletime_assert_147' declared with attribute error: BUILD_BUG_ON failed: (CPU_ENTRY_AREA_PAGES+1)*PAGE_SIZE != CPU_ENTRY_AREA_MAP_SIZE _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__) ^ include/linux/compiler.h:314:4: note: in definition of macro '__compiletime_assert' prefix ## suffix(); \ ^~~~~~ include/linux/compiler.h:334:2: note: in expansion of macro '_compiletime_assert' _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__) ^~~~~~~~~~~~~~~~~~~ include/linux/build_bug.h:47:37: note: in expansion of macro 'compiletime_assert' #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) ^~~~~~~~~~~~~~~~~~ include/linux/build_bug.h:71:2: note: in expansion of macro 'BUILD_BUG_ON_MSG' BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) ^~~~~~~~~~~~~~~~ arch/x86/mm/cpu_entry_area.c:147:2: note: in expansion of macro 'BUILD_BUG_ON' BUILD_BUG_ON((CPU_ENTRY_AREA_PAGES+1)*PAGE_SIZE != CPU_ENTRY_AREA_MAP_SIZE); ^~~~~~~~~~~~ -- Linaro LKFT https://lkft.linaro.org