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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no 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 393BACA9EA0 for ; Tue, 22 Oct 2019 15:47:59 +0000 (UTC) Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by mail.kernel.org (Postfix) with SMTP id 850D1214B2 for ; Tue, 22 Oct 2019 15:47:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 850D1214B2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernel-hardening-return-17086-kernel-hardening=archiver.kernel.org@lists.openwall.com Received: (qmail 8158 invoked by uid 550); 22 Oct 2019 15:47:51 -0000 Mailing-List: contact kernel-hardening-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Received: (qmail 8137 invoked from network); 22 Oct 2019 15:47:50 -0000 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) 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.