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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B6A7C7618A for ; Mon, 20 Mar 2023 11:06:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229723AbjCTLGo (ORCPT ); Mon, 20 Mar 2023 07:06:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230122AbjCTLF5 (ORCPT ); Mon, 20 Mar 2023 07:05:57 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9DCAD2DE5E for ; Mon, 20 Mar 2023 04:00:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679310008; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YvwS21V87OZURkjfZ9iHLFx7wse477fWO8o7cVdC8zE=; b=G7nqLdNRu3U/hpjxUOy5IBjkCZNtz87WkaNzXMMYSvc5ldkjnsXlD/TX5hHsxcbnq1Lb4d LkGUKWQeSUr7Dv9aRRo5VdDBY1PPrGJmzRHy5msGI59BAsmhqw/GLTE8yrnbrPJ9wKx8Sc ZIgkUnSXRNTDaWdQZJbDyrPe4m5FoY4= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-161-hA-HF2aiMUaF63Tq7wp92Q-1; Mon, 20 Mar 2023 07:00:06 -0400 X-MC-Unique: hA-HF2aiMUaF63Tq7wp92Q-1 Received: by mail-wr1-f69.google.com with SMTP id j17-20020adfb311000000b002d660153278so253814wrd.20 for ; Mon, 20 Mar 2023 04:00:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679310005; h=content-transfer-encoding:in-reply-to:organization:from:references :to:content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YvwS21V87OZURkjfZ9iHLFx7wse477fWO8o7cVdC8zE=; b=cjCcGKvhMfY00UBfEHhfNlIkoYPnQILDEIBoVN2NUympYE/bwT+LcgulsFmpnQjAYg M2FR1r0bVlsvJTAYPnCK0DdKqw0kmf8sTdA7Unh5bndtavq0m2n+oEnv4zNSxXErbwbp WVJQzB9SpScATZDMGe8rP+c/Q42CgxvpjXMndPvxhvRWDmjYOLhoesr0k/0IXWgVfMAi zqS2bOnoSCfaooIDU7hscFVPuGPdQ+6trBQgWZSIOkiSp4ypjCiqXUXFvPjaUpCr28xj Hurq+zThTReY9VQiHASMUiZ/qLvpZTJZCYnCnUr0sijwPpqCYhyp/mbDqyllCpSXq4JY bhEQ== X-Gm-Message-State: AO0yUKXmhmkui8kMTnGFYWIa8wxnEC64PIjsJQeBsSbZhZCQ4OYL5R8N tAWHF4npDDAENLkm029wx9SKt2GQClKlJKNTlKHwg5C5iY/Z8G9fsbQjgoivPKbpGJ0qdrtn1QG 6Qt7sQsOyuv8fz9HEoFZJF+Gp X-Received: by 2002:adf:fb01:0:b0:2ce:b7a1:c1a3 with SMTP id c1-20020adffb01000000b002ceb7a1c1a3mr13234763wrr.3.1679310005017; Mon, 20 Mar 2023 04:00:05 -0700 (PDT) X-Google-Smtp-Source: AK7set+Nm/AP50JtymPg9eFJ2hX8KoBE8+/Y4A7ha4GmGX4nlc3yTngMWY2fH+jF7oTeCP5yHiDIEA== X-Received: by 2002:adf:fb01:0:b0:2ce:b7a1:c1a3 with SMTP id c1-20020adffb01000000b002ceb7a1c1a3mr13234726wrr.3.1679310004672; Mon, 20 Mar 2023 04:00:04 -0700 (PDT) Received: from ?IPV6:2003:cb:c702:4100:a064:1ded:25ec:cf2f? (p200300cbc7024100a0641ded25eccf2f.dip0.t-ipconnect.de. [2003:cb:c702:4100:a064:1ded:25ec:cf2f]) by smtp.gmail.com with ESMTPSA id u8-20020adfdb88000000b002cff06039d7sm8616030wri.39.2023.03.20.04.00.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Mar 2023 04:00:04 -0700 (PDT) Message-ID: <94d228b4-3d49-8cb0-a45c-3342c8b1da22@redhat.com> Date: Mon, 20 Mar 2023 12:00:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v8 26/40] mm: Warn on shadow stack memory in wrong vma Content-Language: en-US To: Rick Edgecombe , 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 , Weijiang Yang , "Kirill A . Shutemov" , John Allen , kcc@google.com, eranian@google.com, rppt@kernel.org, jamorris@linux.microsoft.com, dethoma@microsoft.com, akpm@linux-foundation.org, Andrew.Cooper3@citrix.com, christina.schimpe@intel.com, debug@rivosinc.com, szabolcs.nagy@arm.com References: <20230319001535.23210-1-rick.p.edgecombe@intel.com> <20230319001535.23210-27-rick.p.edgecombe@intel.com> From: David Hildenbrand Organization: Red Hat In-Reply-To: <20230319001535.23210-27-rick.p.edgecombe@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19.03.23 01:15, Rick Edgecombe wrote: > The x86 Control-flow Enforcement Technology (CET) feature includes a new > type of memory called shadow stack. This shadow stack memory has some > unusual properties, which requires some core mm changes to function > properly. > > One sharp edge is that PTEs that are both Write=0 and Dirty=1 are > treated as shadow by the CPU, but this combination used to be created by > the kernel on x86. Previous patches have changed the kernel to now avoid > creating these PTEs unless they are for shadow stack memory. In case any > missed corners of the kernel are still creating PTEs like this for > non-shadow stack memory, and to catch any re-introductions of the logic, > warn if any shadow stack PTEs (Write=0, Dirty=1) are found in non-shadow > stack VMAs when they are being zapped. This won't catch transient cases > but should have decent coverage. It will be compiled out when shadow > stack is not configured. > > In order to check if a PTE is shadow stack in core mm code, add two arch > breakouts arch_check_zapped_pte/pmd(). This will allow shadow stack > specific code to be kept in arch/x86. > > Signed-off-by: Rick Edgecombe > Reviewed-by: Kees Cook > Acked-by: Mike Rapoport (IBM) > Tested-by: Pengfei Xu > Tested-by: John Allen > Tested-by: Kees Cook Acked-by: David Hildenbrand -- Thanks, David / dhildenb