Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp5769881imm; Mon, 23 Jul 2018 05:54:09 -0700 (PDT) X-Google-Smtp-Source: AAOMgpd/4fwg4WnFC8SMfyOcPLaBw3yppYJArQoxNQe0N8Epi7NM8zX7ySQUSHUVE+VZ7AD8HNoD X-Received: by 2002:a63:5fc1:: with SMTP id t184-v6mr11719686pgb.183.1532350449601; Mon, 23 Jul 2018 05:54:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532350449; cv=none; d=google.com; s=arc-20160816; b=ab8k4zNDpQtCxBINVyiCE4C/eSlOdIF9Wg48E4m+aEoeAXnYdKr8H01enaoeIC44GX 7Ic92o/3NPTOxbcGk24ujjhKZPqMnk9KRm53giN3TPSBMwlBp1L6N1/M3Cb49hqp5Rqd iu6S8F7hm3p4iWzxy3oWh+UU0GwLqRwABcE5aFuWbUDsFQrYKjiR2e0JXlwYRcu5L5mS 4DghBmZ9jA29vE4PG4gtT8gEfFDQFVxifLxTcEkkux9Yncf+G+6evL/vQuKtsFAPRs3o gFcR7T1BcRTwryFkfqZ0no6y7uI2hMa5xmfbFPIOHIIIaon8mrmVFsS7+TkK8o0CnTAx idGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=C9VZAjyTD+flA7++iKV6kkB/qjtfJSfF04BUlBj3FeU=; b=lAM7b8UK34fS8CddPBFs5owR9HfqM5o9/BM3hy4hCgL7jeJxcC/5LD4v97WA9tzAwf /Yj8YPtfNOQK8t6vNB0l4z8IuZ0zajPUhYPJtgwxaDBpyh19lPTrBh50Ibz5rc5Dx9NS 5rFexM23Yo22iR0Y9Q3O+zf16SJmnHEHz4wNmqPCmjdWGQdKD79W0gWdXp060ByjvnJo Y7pd89EKlXuZ+9kbskRGAorJYtrp7F1GmvWSeq8bZRg8SFIPJZtxHl2VSKZwVefLQSV3 qyEM4kNTdRyVbpvwjFSfyNsDrHfGd3y2KgmOOFuWBOdQrp/48zOgRRrnYBmVZBUYaneF fPpA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c8-v6si9208440pfc.136.2018.07.23.05.53.55; Mon, 23 Jul 2018 05:54:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388588AbeGWNxX (ORCPT + 99 others); Mon, 23 Jul 2018 09:53:23 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:51134 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388533AbeGWNrs (ORCPT ); Mon, 23 Jul 2018 09:47:48 -0400 Received: from localhost (LFbn-1-12238-233.w90-92.abo.wanadoo.fr [90.92.53.233]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id C0ED1C74; Mon, 23 Jul 2018 12:45:32 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Arnd Bergmann , Thomas Gleixner , Ricardo Neri , Andy Lutomirski , Borislav Petkov , Thomas Garnier , David Woodhouse , "Srivatsa S. Bhat" , "Matt Helsley (VMware)" , Alexey Makhalov , Bo Gan Subject: [PATCH 4.4 028/107] x86/pti: Mark constant arrays as __initconst Date: Mon, 23 Jul 2018 14:41:22 +0200 Message-Id: <20180723122414.231803248@linuxfoundation.org> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20180723122413.003644357@linuxfoundation.org> References: <20180723122413.003644357@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 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 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Arnd Bergmann (cherry picked from commit 4bf5d56d429cbc96c23d809a08f63cd29e1a702e) I'm seeing build failures from the two newly introduced arrays that are marked 'const' and '__initdata', which are mutually exclusive: arch/x86/kernel/cpu/common.c:882:43: error: 'cpu_no_speculation' causes a section type conflict with 'e820_table_firmware_init' arch/x86/kernel/cpu/common.c:895:43: error: 'cpu_no_meltdown' causes a section type conflict with 'e820_table_firmware_init' The correct annotation is __initconst. Fixes: fec9434a12f3 ("x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown") Signed-off-by: Arnd Bergmann Signed-off-by: Thomas Gleixner Cc: Ricardo Neri Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Thomas Garnier Cc: David Woodhouse Link: https://lkml.kernel.org/r/20180202213959.611210-1-arnd@arndb.de Signed-off-by: David Woodhouse Signed-off-by: Greg Kroah-Hartman Signed-off-by: Srivatsa S. Bhat Reviewed-by: Matt Helsley (VMware) Reviewed-by: Alexey Makhalov Reviewed-by: Bo Gan Signed-off-by: Greg Kroah-Hartman --- arch/x86/kernel/cpu/common.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/arch/x86/kernel/cpu/common.c +++ b/arch/x86/kernel/cpu/common.c @@ -817,7 +817,7 @@ static void identify_cpu_without_cpuid(s #endif } -static const __initdata struct x86_cpu_id cpu_no_speculation[] = { +static const __initconst struct x86_cpu_id cpu_no_speculation[] = { { X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_CEDARVIEW, X86_FEATURE_ANY }, { X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_CLOVERVIEW, X86_FEATURE_ANY }, { X86_VENDOR_INTEL, 6, INTEL_FAM6_ATOM_LINCROFT, X86_FEATURE_ANY }, @@ -830,7 +830,7 @@ static const __initdata struct x86_cpu_i {} }; -static const __initdata struct x86_cpu_id cpu_no_meltdown[] = { +static const __initconst struct x86_cpu_id cpu_no_meltdown[] = { { X86_VENDOR_AMD }, {} };