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=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL 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 91976CA9ECF for ; Fri, 1 Nov 2019 20:33:18 +0000 (UTC) Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by mail.kernel.org (Postfix) with SMTP id CFB162086D for ; Fri, 1 Nov 2019 20:33:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="llfdsR0m" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CFB162086D Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernel-hardening-return-17230-kernel-hardening=archiver.kernel.org@lists.openwall.com Received: (qmail 32045 invoked by uid 550); 1 Nov 2019 20:33:11 -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 32025 invoked from network); 1 Nov 2019 20:33:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4dKpzKxgNAxP7uchZEE718nvYJMIp2XAO+c9cDo3MTw=; b=llfdsR0mFeyjibNMIjs4xEF9RnIEM/F4fsan8LefCEHgwtIYNAOKIWcaMLXCPUXpJ6 A9Z8a1hAgX5vph4HYseMN3OqV8I4aKmmq61yuf71G+j+fbM6F/3QgbQISzZRx++xQ6uQ rpxg24u1nhhkPdYZ+GFUsMLFT0BeCg+0eevZt88sPMVsXoz6DTHteeXsogaoUL2SzY9v ghKr14XCTinh2/ic+0QjTvbuoVjhyxGzJVQN5RBRvaOEv1Ld5FTshxsndE4TaEObzpiZ /X2kDb3o7l53lLDAuOgjn1yk+JP4f9YS1pPMkt9P5uzVOg4IpQmpskO8NUzz8gBdCY7Z QN9g== 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=4dKpzKxgNAxP7uchZEE718nvYJMIp2XAO+c9cDo3MTw=; b=ENcX8lva7uyHYky3nspbcW13N42MbHzn4cF5fhnHd4NAHb+d2GQVlc+OH30HHUtW1j 1TTZMGGFGoKbNLVsHPFbKf2kyXMSHNjSkqTJiXM91Z1vo+K6OjjOGzrQ801fEZA5ybXT uPJWnkEJ6qb3BNjKcYpjHbic41AfC8qsFTc1pw3L+XivheOOUVjVc7HLLjndGh3p9/2j nCuUlUQlMpUkBEZ5FnW3CXFLZqDWGc+ILBLZCD1hf85iJegn4yOkGDVL7VXiXx09fKs/ cyTMhfW/CxXAAh75lJhuc/u4heIY/pWY2s0EDgCCSiVMNCb9VD3ej1khr9uw2UHgc+CA MBJA== X-Gm-Message-State: APjAAAVBDZxwnQfO3l19tD9AsdsLLTOpQa8uj5b15E2EsKLPvixtcg97 67U3LAFiKZuSYsATvXu5oliEKcGKdlakCucZtIcHbA== X-Google-Smtp-Source: APXvYqyDyHEaxIBZlzITcLvjh/p5XeQ4QgzocUuUCOwXN0WOuNqq+ARu4A8BUTsto1yGSfnwMlhvbSnvYIziXBMnd3E= X-Received: by 2002:a67:e88f:: with SMTP id x15mr1725327vsn.5.1572640378099; Fri, 01 Nov 2019 13:32:58 -0700 (PDT) MIME-Version: 1.0 References: <20191018161033.261971-1-samitolvanen@google.com> <20191031164637.48901-1-samitolvanen@google.com> <20191031164637.48901-12-samitolvanen@google.com> <201910312056.E3315F0F@keescook> In-Reply-To: <201910312056.E3315F0F@keescook> From: Sami Tolvanen Date: Fri, 1 Nov 2019 13:32:46 -0700 Message-ID: Subject: Re: [PATCH v3 11/17] arm64: disable function graph tracing with SCS To: Kees Cook Cc: Will Deacon , Catalin Marinas , Steven Rostedt , Masami Hiramatsu , Ard Biesheuvel , Dave Martin , Laura Abbott , Mark Rutland , Nick Desaulniers , Jann Horn , Miguel Ojeda , Masahiro Yamada , clang-built-linux , Kernel Hardening , linux-arm-kernel , LKML Content-Type: text/plain; charset="UTF-8" On Thu, Oct 31, 2019 at 8:58 PM Kees Cook wrote: > IIRC, the argument was to disable these on a per-arch basis instead of > doing it as a "depends on !SHADOW_CALL_STACK" in the top-level function > graph tracer Kconfig? Yes, that's correct. > (I'm just thinking ahead to doing this again for > other architectures, though, I guess, there is much more work than just > that for, say, x86.) We can always change this later if needed, and possibly figure out how to make function graph tracing and kretprobes work with SCS. Sami