Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1430828pxf; Fri, 9 Apr 2021 08:14:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxxp1iirR2gI9J9SfwhJBrpyhhJ76aNa+DhBWYluzOJNnRmuc2mjx/O+L/bMfQ9+2+LlEhl X-Received: by 2002:a17:907:d1f:: with SMTP id gn31mr16499713ejc.536.1617981292506; Fri, 09 Apr 2021 08:14:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617981292; cv=none; d=google.com; s=arc-20160816; b=Fug3TUOgPwEOpgbO668oWQgzAQExNny0crhdHJzPMlJknKBKy3GMVGpPn/Sn/28Fwb qiLs1D+W/ZcNso2GJ+EPiguPZ6QbqPyyF5yI/71MnipWHguDTVWdEj1dhCCdPI2evZ9h 5zMxaob3Pf5s1hTfyP1le7mFr9p7h0h18Fy+k2ODEeZjOkrroQKh0gc39tTsS98WhZb+ LNdcXzOIqm9Z4FHF/0fmg0C4pEJpUtbgDqy4bWky8CtIHYy+mNSgqpm3UqV39NGSVN8p gaBE5dDvKNkwtYigskngt+jZxandu7I++8txrPM18TmM6mY3jZizG+HMF8KDdqTe+lQd R6zA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=PDyMSJJvLIMFC1KbCjmLHB5PTIgl8fLhsjpA7s8Yb6Q=; b=YtPLMxIbGnHWYGfciSFE5clDw9lY5l9SxJ0cmxVvX8xRjR86EfcxKWxlskm451etCd ggVyit8djPTOO/5UMRvZZ0KZHYnAIBupvQ82ndebN9Cud2nfIq8efBzL8aPUPPU4FVw5 RtsVb/p06sAytg4Zq8mQENocV2dt/LJxFu0RhNphEGpaqeCn2b/K9y+lbfqi9FDge1rC U3vNv9jeO7EDLqqIAJXBCsMnu5g3wTRnWmOXKVrp1c1ZYLEzdfaLfvwfRD2aWJSjEvyw QI0paaUsHa94jxD46u1hZGbaPWTleHKwAw6AQ623gh4ty6sbd8iQIsTWa2IJjwbH8/eM ARzA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b=WUE6Vxis; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t22si2022869ejj.746.2021.04.09.08.14.27; Fri, 09 Apr 2021 08:14:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b=WUE6Vxis; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234113AbhDIPMm (ORCPT + 99 others); Fri, 9 Apr 2021 11:12:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37882 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234111AbhDIPMk (ORCPT ); Fri, 9 Apr 2021 11:12:40 -0400 Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ACB4CC061763 for ; Fri, 9 Apr 2021 08:12:27 -0700 (PDT) Received: by mail-lf1-x12f.google.com with SMTP id x13so89008lfr.2 for ; Fri, 09 Apr 2021 08:12:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shutemov-name.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=PDyMSJJvLIMFC1KbCjmLHB5PTIgl8fLhsjpA7s8Yb6Q=; b=WUE6Vxis/wkboifvaP4/0mKQH9ZqXTXg09FLow2NBClwREFinJQQ7Ym269+P2rGdYS H8OWs7F1iSt6G0pM1qTUlLYbVDnQPeqAXBmP92LWmtN69zpGrjqmOrTUUlRTZHR8pogT HSxBDs2fiYTfAa+HHPHzSFp+8beCoBX+rQifO+DG79+wglkVBUUlIFhyZuhQz4JHNwqk kPJS1NjJ+V/xdMmrwNrtSJB7PzFZN5PhPjT2q6jGA2WKNNSR3+/AURsA2gkd01+BcMhd 0LXY1hEnpKIJdbbkNFmtfPJLm1ibRZPKLfbAtJRACzTh3QzzHpzbwLEb4YDGLWvW7amr s2bA== 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=PDyMSJJvLIMFC1KbCjmLHB5PTIgl8fLhsjpA7s8Yb6Q=; b=EJqEzJlqSHw3gKLDvreeIy6iSyMN9+Ex+Su8OYJu6gh4gSSJrsY2DwoJpv6WzEzsjY R/4anD1ERuRLOR4+18sKq1wdeiJKTUFFXZ/1sH7l+TPx+W8rtnLcaQCWE/Y6bcPGrcjz 3JIb733azHUZ4V4aALNft441mj8VXmVnkRrrHJ63pEuJbUkG/0YvQ/CnCliPo6hcxVaD /tZjYaZeGVp5gaCU+7Gp4qq9q5oGnMprM8LwMY2S4TnGE20l5UZvbYARD3WttNuZv7CW BYGDaCHyzBjcvJWbsaJGTvfL2J3szxMqlKC1nuSLlxj8yb11U+GXMmL7K8if/rqIvJjF Vk3Q== X-Gm-Message-State: AOAM530qOFA8R30E12v0UyOYhstYDtX3PJE6Qm4k25R6zGT1I19rFjQj SnTpYo0tRSsEtcvdtpDpPtRMDA== X-Received: by 2002:a19:8c0a:: with SMTP id o10mr10600843lfd.175.1617981146160; Fri, 09 Apr 2021 08:12:26 -0700 (PDT) Received: from box.localdomain ([86.57.175.117]) by smtp.gmail.com with ESMTPSA id k18sm295287lfg.32.2021.04.09.08.12.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Apr 2021 08:12:25 -0700 (PDT) Received: by box.localdomain (Postfix, from userid 1000) id 05C1F102498; Fri, 9 Apr 2021 18:12:25 +0300 (+03) Date: Fri, 9 Apr 2021 18:12:24 +0300 From: "Kirill A. Shutemov" 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 , Kees Cook , Mike Kravetz , Nadav Amit , Oleg Nesterov , Pavel Machek , Peter Zijlstra , Randy Dunlap , "Ravi V. Shankar" , Vedvyas Shanbhogue , Dave Martin , Weijiang Yang , Pengfei Xu , Haitao Huang , "Kirill A . Shutemov" Subject: Re: [PATCH v24 14/30] x86/mm: Shadow Stack page fault error checking Message-ID: <20210409151224.4tlklypbjpxcztpt@box.shutemov.name> References: <20210401221104.31584-1-yu-cheng.yu@intel.com> <20210401221104.31584-15-yu-cheng.yu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210401221104.31584-15-yu-cheng.yu@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 01, 2021 at 03:10:48PM -0700, Yu-cheng Yu wrote: > Shadow stack accesses are those that are performed by the CPU where it > expects to encounter a shadow stack mapping. These accesses are performed > implicitly by CALL/RET at the site of the shadow stack pointer. These > accesses are made explicitly by shadow stack management instructions like > WRUSSQ. > > Shadow stacks accesses to shadow-stack mapping can see faults in normal, > valid operation just like regular accesses to regular mappings. Shadow > stacks need some of the same features like delayed allocation, swap and > copy-on-write. > > Shadow stack accesses can also result in errors, such as when a shadow > stack overflows, or if a shadow stack access occurs to a non-shadow-stack > mapping. > > In handling a shadow stack page fault, verify it occurs within a shadow > stack mapping. It is always an error otherwise. For valid shadow stack > accesses, set FAULT_FLAG_WRITE to effect copy-on-write. Because clearing > _PAGE_DIRTY (vs. _PAGE_RW) is used to trigger the fault, shadow stack read > fault and shadow stack write fault are not differentiated and both are > handled as a write access. > > Signed-off-by: Yu-cheng Yu > Reviewed-by: Kees Cook Reviewed-by: Kirill A. Shutemov -- Kirill A. Shutemov