Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp5906715ybg; Tue, 22 Oct 2019 10:04:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqyrqS5Qe8ABWyv76ZdRT1rd3uDqz+/8447Ig/fVFK1IZ62a0ZqkMsKkcdDQFGhUwhi8JVMh X-Received: by 2002:a05:6402:128c:: with SMTP id w12mr32860357edv.284.1571763896851; Tue, 22 Oct 2019 10:04:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571763896; cv=none; d=google.com; s=arc-20160816; b=I1HEYwxjcKEIqyIKSzQcdmIYfn7kNYHW6cEoq8X1BUIg2Uzw3HIhlSSJ5pripFYPPJ 4Eb+8F9PvAIU3KAQNXD2ZzhJBrnPZeo/otIb2T5LryiXJExCNjqDYeI7afxR3HIxAUup SCaZEfp0m0PSVL7J8dHd1BrJL7lp4eHe5uDlOFC8SPUAJ37meKq0h4f4f8TBVhTX1EdN d2dsktv8ivV8OlOdljweJGnkpcmpb5gTY7wQmu5fAmi7vd49IXdBrS0o4PdaPz7XAaFb J79psry+s9UeLRxkbXR7Lh8Motyk3Y0qKkcqZ3KRsFaRbZnSGd+ZMoqeblgPzGXLFvVp bV+w== 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; bh=hnSXl26RwlZH/A0zSyDK2IGAooS2oMUmHEZVFk6VFdY=; b=0fnavq+tmA2hDqVsUtoRdqCq5HLBgNrA2cDwVLEB0ncWjB1LEPT0vTWTXT91Z4Td8P Onbv6DjMGJRiNOO/rkUjZ2i6Fbc6rCVsjQO9qEp4tMGA6l7cJnkz/ahRcmaqAw6lQyhe EHokPFPOGHhh3s9MKxTmQA1m+NYvCZ5NZA0pOQS8+C9PSxqtdL3rdldxnVUtMxJaLLcP Z6vgsm6s8rNYQ5Pf0XaERmLrt3e8gbAynBHggXCpNjhiFFqpmK5LyEQ+jQS98wATjKF9 58JrIUMK5/TnIJCbPMnvUK5edw/GlRNFlA/Iz5G/bywQImziXpMLTAlcijd/zlvg2YbJ fynA== 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 h40si8070769ede.176.2019.10.22.10.04.31; Tue, 22 Oct 2019 10:04:56 -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 S2387794AbfJVPrl (ORCPT + 99 others); Tue, 22 Oct 2019 11:47:41 -0400 Received: from [217.140.110.172] ([217.140.110.172]:55818 "EHLO foss.arm.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1730141AbfJVPrl (ORCPT ); Tue, 22 Oct 2019 11:47:41 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 977AC177F; Tue, 22 Oct 2019 08:47:18 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E54FC3F71A; Tue, 22 Oct 2019 08:47:16 -0700 (PDT) Date: Tue, 22 Oct 2019 16:47:08 +0100 From: Mark Rutland To: Sami Tolvanen Cc: Will Deacon , Catalin Marinas , Steven Rostedt , Ard Biesheuvel , Dave Martin , Kees Cook , Laura Abbott , Nick Desaulniers , clang-built-linux , Kernel Hardening , linux-arm-kernel , LKML Subject: Re: [PATCH 13/18] arm64: preserve x18 when CPU is suspended Message-ID: <20191022154708.GA699@lakrids.cambridge.arm.com> References: <20191018161033.261971-1-samitolvanen@google.com> <20191018161033.261971-14-samitolvanen@google.com> <20191021165649.GE56589@lakrids.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 21, 2019 at 03:43:14PM -0700, Sami Tolvanen wrote: > On Mon, Oct 21, 2019 at 9:56 AM Mark Rutland wrote: > > This should have a corresponding change to cpu_suspend_ctx in > > . Otherwise we're corrupting a portion of the stack. > > Ugh, correct. I'll fix this in the next version. Thanks. It's probably worth extending the comment above cpu_do_suspend to say: | This must be kept in sync with struct cpu_suspend_ctx in | ... to match what we have above struct cpu_suspend_ctx, and make this more obvious in future. Thanks, Mark.