Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1246532ybx; Tue, 5 Nov 2019 12:51:57 -0800 (PST) X-Google-Smtp-Source: APXvYqwV+8b51XEhoezQyEwMBNjNlFW1eWshCkgbZ8ReU6/anZ8WIn1ABtBMnGmAdlGqtjbNX8U8 X-Received: by 2002:a50:b4e4:: with SMTP id x33mr6281680edd.222.1572987117279; Tue, 05 Nov 2019 12:51:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572987117; cv=none; d=google.com; s=arc-20160816; b=llDJBPahlqnA3eKAP9C3KLDumehsPkk5F2OD6npNsFKwD6cu5rtV6/YSc+lFmCo2Vr CdG5CHd2kNTIgP78+DnikRdD0+v3iG6WLqaUQoUUNJJkYuU8r+xLj9DxswArLIGhEJIs WEayUs/WNbwP3gd+NNYR7V7COE4um9CJaBx9Gf1pdZaFNFwICM7JGh4wcK8rQS5rFYfG nnXemFb+ddYvX026zlz+2G947yJgNT7f5OSG0nI4F1Cf7BvKIZFsRPvv6bICsnvOZVCa ingxyE8J38kQU1qJM1ZS+m6umjksqqD4K3xyFH9qQ/uQwevCdO2Pf3Yo8SuhZZNC88Pz hoHw== 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=Tv31pLwVHFJyy3TUZMQ/vDmJ8BgCr4RBZFLf8nQZGlo=; b=k6xYYyAIO68dtmVyP7XptQjTTP8fQeYcRR7AmBTSHEIZ8W8UIvRN1TksWaHiO7e/pU 7gs/nZ3XU0hIRd9JxW9hSC8edptw09Q7g110Tl1jLBh/q/Zt0Xc+f7mWO3XimhS329QA BlsPxR61qnv7+jhjIPXkDmhKtVrxduk3tFXyxCLtuSscjv88UwdRSMJYd9z5ZOOM+9ma D46fnrJ1kAMkd68QF9MYhDu9sUmFv8mqIu8yUhEhe+DFdx7dJ0v2UpNpOrXUDCkHzQf9 QAvp2/QqivqXjmPB7ePcq1tVA/NvJ5HHPEgox3JKB9Wr1F0H18amkgwcRYBrNUUpJ9Jl HYfw== 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 b53si10660177edb.419.2019.11.05.12.51.33; Tue, 05 Nov 2019 12:51:57 -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 S1729795AbfKEUt6 (ORCPT + 99 others); Tue, 5 Nov 2019 15:49:58 -0500 Received: from foss.arm.com ([217.140.110.172]:32788 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727888AbfKEUt5 (ORCPT ); Tue, 5 Nov 2019 15:49:57 -0500 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 DEAD111B3; Tue, 5 Nov 2019 12:49:56 -0800 (PST) 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 9AD203FB7F; Tue, 5 Nov 2019 01:04:38 -0800 (PST) Date: Tue, 5 Nov 2019 09:04:26 +0000 From: Mark Rutland To: Sami Tolvanen Cc: Will Deacon , Catalin Marinas , Steven Rostedt , Masami Hiramatsu , Ard Biesheuvel , Dave Martin , Kees Cook , Laura Abbott , Marc Zyngier , Nick Desaulniers , Jann Horn , Miguel Ojeda , Masahiro Yamada , clang-built-linux , Kernel Hardening , linux-arm-kernel , LKML Subject: Re: [PATCH v4 10/17] arm64: disable kretprobes with SCS Message-ID: <20191105090426.GA4743@lakrids.cambridge.arm.com> References: <20191018161033.261971-1-samitolvanen@google.com> <20191101221150.116536-1-samitolvanen@google.com> <20191101221150.116536-11-samitolvanen@google.com> <20191104170454.GA2024@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, Nov 04, 2019 at 03:42:09PM -0800, Sami Tolvanen wrote: > On Mon, Nov 4, 2019 at 9:05 AM Mark Rutland wrote: > > I'm a bit confused as to why that's the case -- could you please > > elaborate on how this is incompatible? > > > > IIUC kretrobes works by patching the function entry point with a BRK, so > > that it can modify the LR _before_ it is saved to the stack. I don't see > > how SCS affects that. > > You're correct. While this may not be optimal for reducing attack > surface, I just tested this to confirm that there's no functional > conflict. I'll drop this and related patches from v5. Great; thanks for confirming! Mark.