Received-SPF: pass (google.com: domain of linux-kernel+bounces-215627-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Fri, 14 Jun 2024 18:12:13 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: jeffxu@chromium.org
Cc: jannh@google.com, sroettger@google.com, rdunlap@infradead.org,
 david@redhat.com, adhemerval.zanella@linaro.org,
 linux-kernel@vger.kernel.org, linux-mm@kvack.org, jorgelo@chromium.org,
 keescook@chromium.org
Subject: Re: [PATCH v2 1/1] /proc/pid/smaps: add mseal info for vma
Message-Id: <20240614181213.3d42b3c3a031acd742349695@linux-foundation.org>
In-Reply-To: <20240614232014.806352-2-jeffxu@google.com>
References: <20240614232014.806352-1-jeffxu@google.com>
	<20240614232014.806352-2-jeffxu@google.com>
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 14 Jun 2024 23:20:14 +0000 jeffxu@chromium.org wrote:

> From: Jeff Xu <jeffxu@chromium.org>
> 
> Add sl in /proc/pid/smaps to indicate vma is sealed
> 
> ...
>
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -571,6 +571,7 @@ encoded manner. The codes are the following:
>      um    userfaultfd missing tracking
>      uw    userfaultfd wr-protect tracking
>      ss    shadow stack page
> +    sl    sealed
>      ==    =======================================

I'll queue this for 6.10-rcX as a fix for 8be7258aad44 ("mseal: add
mseal syscall").