Received: by 10.223.185.116 with SMTP id b49csp834702wrg; Wed, 14 Feb 2018 07:41:58 -0800 (PST) X-Google-Smtp-Source: AH8x225sBk9JasEAktNB8LHymq4ppmHr/xxuFjfSu4n1iIGCCUMYGGOi/oBy79S3uYE0Oy6O4H5D X-Received: by 10.99.116.25 with SMTP id p25mr4291657pgc.109.1518622918866; Wed, 14 Feb 2018 07:41:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518622918; cv=none; d=google.com; s=arc-20160816; b=BFRFDBCkqq96M03MA29isG4J4vgMogc22in2RQBjV8/mWvf071ztfkYMoUEpAYgPhF sUVWKRH0g6QhY9Vz1E72VU+Nqt2hhuAm05JoKVWi7AopTvPdmPnxiFKuGMgS23vF2iEI RDlxyVJZLTvFx+ebQNyQdRPtCQWAmm3N+YeSHEUMkCgC+t4zrhqtMg1Z5r1Vh5U3Np3h Ey2ig0oPtoQi6uWIPX5uKT2n1IlO39UJ3xAac1GLPGvJIj0TZJKd9Uaeh9Tb1VKADA6H pqZAk7KVfNVrtXT26BC4zMBx79KStyv3s44Y9je3CoiH8PXvY6zQBaYHUwmx4I8fypY7 OUeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=aQIej1AFLwo2KDbmQJgqwJePX6cvAtTWF84YCWOvSwM=; b=I/Ss8b6Qf5QlOJXkvxH81O/6eRdnS+zxmH1yFGjcs9WIRJxkwvAwaPAykwKVdpUq79 un+IpqN7q+r1RKg0j3WS+dSK4jtfszWu2Yt+U6GkXmgfRDNSzpTKFcnXyRT/nLMoEoMY xacHIqA71K/4WAtOQAU7HtpIMdvsDWj9RL+USFUQ+jK39OkKbIp14+fdwD8ROY0aX1Wt gm1OHlmrfXrA41XPGoJScGpTCS0FeOzPP+4SeWHcTL1pZ6n820MCOYnw0rg8v8q9c9iO gEc7pHC/A2ACOgQcNltV09BzMt6bR2kl1aL1OvEN6C/iDIuWtO86w0zcl835193xi6jX KnMA== 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 w4si1050432pgq.199.2018.02.14.07.41.43; Wed, 14 Feb 2018 07:41:58 -0800 (PST) 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 S1031627AbeBNPkf (ORCPT + 99 others); Wed, 14 Feb 2018 10:40:35 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:50824 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031511AbeBNPke (ORCPT ); Wed, 14 Feb 2018 10:40:34 -0500 Received: from localhost (unknown [37.171.180.34]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id AC1A31160; Wed, 14 Feb 2018 15:40:33 +0000 (UTC) Date: Wed, 14 Feb 2018 16:40:33 +0100 From: Greg KH To: Ard Biesheuvel Cc: stable@vger.kernel.org, Linux Kernel Mailing List , Will Deacon , Catalin Marinas , Marc Zyngier , Mark Brown , linux-arm-kernel Subject: Re: [GIT PULL] arm64 spectre and meltdown mitigations for v4.14-stable Message-ID: <20180214154033.GA2745@kroah.com> References: <20180212113801.2552-1-ard.biesheuvel@linaro.org> <20180214135420.GB24189@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 14, 2018 at 02:34:01PM +0000, Ard Biesheuvel wrote: > On 14 February 2018 at 14:24, Ard Biesheuvel wrote: > > On 14 February 2018 at 13:54, Greg KH wrote: > >> On Mon, Feb 12, 2018 at 11:38:01AM +0000, Ard Biesheuvel wrote: > >>> Hi Greg, > >>> > >>> As mentioned by Will, I have created the v4.14 counterpart of his stable > >>> backport of the arm64/ARM Spectre/Meltdown mitigations that have been pulled > >>> into v4.16-rc1. > >>> > >>> Given that this is the v4.15 version backported to v4.14, I have removed any > >>> mention of 'conflicts' from the commit logs as they are now ambiguous. The > >>> patches applied surprisingly cleanly, I only needed to drop two patches that > >>> are already in (the same ones Will mentioned in his PR), and drop another one > >>> dealing with SPE, support for which did not exist yet in v4.14. I also included > >>> the patch > >>> > >>> arm64: move TASK_* definitions to > >>> > >>> from v4.15 to make Robin's Spectre v1 patches apply more cleanly. > >> > >> I've queued these up now, but if you could pull the whole quilt tree and > >> verify I got things right, that would be great. There was some > >> conflicts with a few previous patches I had already queued up that > >> touched some "Falkor" errata code. > >> > >> Specifically 932b50c7c1c65e6f23002e075b97ee083c4a9e71 "arm64: Add > >> software workaround for Falkor erratum 1041" is the offending patch. I > >> think I resolved the merge issues properly, but verifying this would be > >> wonderful. > >> > > > > No, the build is broken now. I will investigate. > > Your patch 977c3d2cb684e143a18e1564fbf5ecf7576a1c98 > > arm64: Move post_ttbr_update_workaround to C code > > removes the pre_disable_mmu_workaround macro from asm/assembler.h but > it should only remove post_ttbr_update_workaround > > Once I add that back, things seem to build and run as expected. Can you provide a "fixed" version of just this patch so I know to get it correct? thanks, greg k-h