[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v6 8/8] memfd_create.2: Describe MFD_INACCESSIBLE flag
From: |
Chao Peng |
Subject: |
[PATCH v6 8/8] memfd_create.2: Describe MFD_INACCESSIBLE flag |
Date: |
Thu, 19 May 2022 23:37:13 +0800 |
Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
---
man2/memfd_create.2 | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
index 89e9c4136..2698222ae 100644
--- a/man2/memfd_create.2
+++ b/man2/memfd_create.2
@@ -101,6 +101,19 @@ meaning that no other seals can be set on the file.
.\" FIXME Why is the MFD_ALLOW_SEALING behavior not simply the default?
.\" Is it worth adding some text explaining this?
.TP
+.BR MFD_INACCESSIBLE
+Disallow userspace access through ordinary MMU accesses via
+.BR read (2),
+.BR write (2)
+and
+.BR mmap (2).
+The file size cannot be changed once initialized.
+This flag cannot coexist with
+.B MFD_ALLOW_SEALING
+and when this flag is set, the initial set of seals will be
+.B F_SEAL_SEAL,
+meaning that no other seals can be set on the file.
+.TP
.BR MFD_HUGETLB " (since Linux 4.14)"
.\" commit 749df87bd7bee5a79cef073f5d032ddb2b211de8
The anonymous file will be created in the hugetlbfs filesystem using
--
2.17.1
- [PATCH v6 3/8] mm/memfd: Introduce MFD_INACCESSIBLE flag, (continued)
[PATCH v6 5/8] KVM: Add KVM_EXIT_MEMORY_FAULT exit, Chao Peng, 2022/05/19
[PATCH v6 6/8] KVM: Handle page fault for private memory, Chao Peng, 2022/05/19
[PATCH v6 7/8] KVM: Enable and expose KVM_MEM_PRIVATE, Chao Peng, 2022/05/19
[PATCH v6 8/8] memfd_create.2: Describe MFD_INACCESSIBLE flag,
Chao Peng <=