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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 184FFC432C3 for ; Wed, 13 Nov 2019 18:33:59 +0000 (UTC) Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by mail.kernel.org (Postfix) with SMTP id B79AD206F0 for ; Wed, 13 Nov 2019 18:33:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="gLQ0w0Ix" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B79AD206F0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernel-hardening-return-17356-kernel-hardening=archiver.kernel.org@lists.openwall.com Received: (qmail 16303 invoked by uid 550); 13 Nov 2019 18:33:52 -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 16277 invoked from network); 13 Nov 2019 18:33:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=OhPSTTe4Xdz6gOjsaJlaEdC5pAfYubYxDCg4SrgVoSo=; b=gLQ0w0IxUEQnchYuilJR1nbU4m7SgY//cNaWQR/mt0lvyefOxSBkOsqifZytiwFIh0 GkBnn3qUVJAEMrTsVlq+svxxCP/slE/95ux0WpqRsVgnTHuEvwwCdJWa6c+0L9ne+iP7 6ydiQoWKF8IYJkGO42ArzjKHFxLH3sDY6CwOk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=OhPSTTe4Xdz6gOjsaJlaEdC5pAfYubYxDCg4SrgVoSo=; b=guJ+5U7OWDJs+fJyOnNNUCg8V8x1LFWzuBYJpBSIW0RPTQnAmD7IkO+NILJxhBCGk1 gXZU8HxQsPLx/XUn0/xFXRJilGHkHhYWqzrmv3ZO73sMWzgvRYzMUBtYnxhtqLDF2cHf 8xwXUKZP+FdHhaD4zBGFwUdJRvuJi/U081VhD16Ynkx/aOruyy8bAboYQosMebxg4lx/ ykY8PsIARASSNsG8aCbUpjbSlm2f9kEDLfXeMgeu2OVj753eXZ3+K5FcIbFlB2HUNCVz iuOlwqnYwCmozwvsTXnrV2SYBDOBZJKEUPS5tqosSF5483/lqLVrExQ3j54StAWo/sEY NIjg== X-Gm-Message-State: APjAAAWl087w6ip95FSVCxPD3yYuvZ6EOJsy1FI9ke8zzkLKIRd8MXlG iZKc5oDSeFUOS6h6Fyqadr5KMg== X-Google-Smtp-Source: APXvYqyLkzEBHbWiCqJacPQ3CBKaBpCEr8iph2zitT6ozdOmqjw+YxPYFt/3IfvrDawkJj7K8FBEVg== X-Received: by 2002:a62:20e:: with SMTP id 14mr6074555pfc.153.1573670020389; Wed, 13 Nov 2019 10:33:40 -0800 (PST) Date: Wed, 13 Nov 2019 10:33:38 -0800 From: Kees Cook To: Will Deacon Cc: Catalin Marinas , Mark Rutland , Sami Tolvanen , Steven Rostedt , Masami Hiramatsu , Ard Biesheuvel , Dave Martin , Laura Abbott , Marc Zyngier , Nick Desaulniers , Jann Horn , Miguel Ojeda , Masahiro Yamada , clang-built-linux@googlegroups.com, kernel-hardening@lists.openwall.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 00/14] add support for Clang's Shadow Call Stack Message-ID: <201911131033.435C8F77D@keescook> References: <20191018161033.261971-1-samitolvanen@google.com> <20191105235608.107702-1-samitolvanen@google.com> <201911121530.FA3D7321F@keescook> <20191113120337.GA26599@willie-the-truck> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191113120337.GA26599@willie-the-truck> On Wed, Nov 13, 2019 at 12:03:38PM +0000, Will Deacon wrote: > On Tue, Nov 12, 2019 at 03:44:42PM -0800, Kees Cook wrote: > > On Tue, Nov 05, 2019 at 03:55:54PM -0800, Sami Tolvanen wrote: > > > This patch series adds support for Clang's Shadow Call Stack > > > (SCS) mitigation, which uses a separately allocated shadow stack > > > to protect against return address overwrites. More information > > > > Will, Catalin, Mark, > > > > What's the next step here? I *think* all the comments have been > > addressed. Is it possible to land this via the arm tree for v5.5? > > I was planning to queue this for 5.6, given that I'd really like it to > spend some quality time in linux-next. Sounds fine to me; I just wanted to have an idea what to expect. :) Thanks! -- Kees Cook