Received-SPF: pass (google.com: domain of linux-kernel+bounces-215593-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: jeffxu@chromium.org
To: akpm@linux-foundation.org,
	jannh@google.com,
	sroettger@google.com,
	rdunlap@infradead.org,
	david@redhat.com,
	adhemerval.zanella@linaro.org
Cc: linux-kernel@vger.kernel.org,
	linux-mm@kvack.org,
	jorgelo@chromium.org,
	keescook@chromium.org,
	Jeff Xu <jeffxu@chromium.org>
Subject: [PATCH v2 0/1] add mseal to /proc/pid/smaps
Date: Fri, 14 Jun 2024 23:20:13 +0000
Message-ID: <20240614232014.806352-1-jeffxu@google.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

From: Jeff Xu <jeffxu@chromium.org>

Add mseal information in /proc/pid/smaps to indicate the VMA is sealed.

I appreicate Adhemerval Zanella Netto to bring this to my attention. [1]

[1] https://public-inbox.org/libc-alpha/743ac2ce-817b-42ef-a0a1-7edf9a85d8e5@linaro.org/#t

History:

v2:
update from Jann Horn's comments:
- change 'sp' to 'sl'
- change 'sealed page' to 'sealed'
- move VM_SEALED define after VM_ALLOW_ANY_UNCACHED

v1:
https://lore.kernel.org/lkml/20240614182327.752156-1-jeffxu@google.com/

Jeff Xu (1):
  /proc/pid/smaps: add mseal info for vma

 Documentation/filesystems/proc.rst | 1 +
 fs/proc/task_mmu.c                 | 3 +++
 include/linux/mm.h                 | 5 +++++
 mm/internal.h                      | 5 -----
 4 files changed, 9 insertions(+), 5 deletions(-)

-- 
2.45.2.627.g7a2c4fd464-goog