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 F0B4DC35E17 for ; Tue, 25 Feb 2020 21:31:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C7F9920838 for ; Tue, 25 Feb 2020 21:31:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="bsIBaiOx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726827AbgBYVba (ORCPT ); Tue, 25 Feb 2020 16:31:30 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:33526 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726465AbgBYVba (ORCPT ); Tue, 25 Feb 2020 16:31:30 -0500 Received: by mail-pf1-f195.google.com with SMTP id n7so262113pfn.0 for ; Tue, 25 Feb 2020 13:31:29 -0800 (PST) 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=rrlr+907qtKDudjoqI94u3BDniTLuSDFOK3CBpzOF4E=; b=bsIBaiOx2q6Nz0szIaHfQPNo4hYm/9YM3ER93MPP+idoUIhz//erff21F8ACX8lvyy /Vtb7KtuLiUG7PmyVOr8JCBZ8gC2CPzmF/IOKIOP6YqVmnN9EltjeteoiuFViaN6gzGA ftBujYT7QwO14ICuSzTpjMUOlrqwxXrSa2li4= 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=rrlr+907qtKDudjoqI94u3BDniTLuSDFOK3CBpzOF4E=; b=qjbE2itd4D0v4db5SyuMDpbIhXTKIS/AfcnJi+TL5qE7LwQRiLxB1PmdLwtItwhnHW cQNZPhEHyxAt54xfEyNHglVen537o8PpgbSIhsd7TOWR3u5Cp9bhVTfK2hTjD2Wcc2o9 VzKacx7ffJoX7FtY1M1mNWeDM1Wgc5t/Ayi4YrOXE+72Xi7oGQcB0f78epAgJgFjjKRc AWDH7qIiKO6cxEEEiMauezrHbPuuWx20hip7HF4g6tcy+GMuvcFdmtcowWkU3nG8+jYv JFFf/dwhxmL0RjXH1ytuyNZ/NWPFYrboi6Plcf4XzQSR6uP6nqTzTcnHDEvbV0G2YMed ppFA== X-Gm-Message-State: APjAAAW2MXGCXJtoX8FsVzqOsUSAlH5bvWcD/o+jwtThXn2mUVRadrCI GttfO2niy5Cgs45zbPPHTOhTIQ== X-Google-Smtp-Source: APXvYqzVvUZuW1LsUViX6xfqJvhxOzF3Vucg+hrYDZWfmpFNwnE34eriSoo3DlbkNO1ERPnR/8OPug== X-Received: by 2002:aa7:84c6:: with SMTP id x6mr669697pfn.181.1582666289361; Tue, 25 Feb 2020 13:31:29 -0800 (PST) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id h26sm33487pfr.9.2020.02.25.13.31.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Feb 2020 13:31:28 -0800 (PST) Date: Tue, 25 Feb 2020 13:31:27 -0800 From: Kees Cook To: Yu-cheng Yu Cc: x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Arnd Bergmann , Andy Lutomirski , Balbir Singh , Borislav Petkov , Cyrill Gorcunov , Dave Hansen , Eugene Syromiatnikov , Florian Weimer , "H.J. Lu" , Jann Horn , Jonathan Corbet , Mike Kravetz , Nadav Amit , Oleg Nesterov , Pavel Machek , Peter Zijlstra , Randy Dunlap , "Ravi V. Shankar" , Vedvyas Shanbhogue , Dave Martin , x86-patch-review@intel.com Subject: Re: [RFC PATCH v9 00/27] Control-flow Enforcement: Shadow Stack Message-ID: <202002251330.7CD5EEFA2@keescook> References: <20200205181935.3712-1-yu-cheng.yu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200205181935.3712-1-yu-cheng.yu@intel.com> Sender: linux-api-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org On Wed, Feb 05, 2020 at 10:19:08AM -0800, Yu-cheng Yu wrote: > Control-flow Enforcement (CET) is a new Intel processor feature that blocks > return/jump-oriented programming attacks. Details can be found in "Intel > 64 and IA-32 Architectures Software Developer's Manual" [1]. At v9, this probably isn't RFC any more. :) As mentioned in another patch, I'd really like to see some self tests for this feature. It's relatively complex... -- Kees Cook