From e51b29b5a931a8020de3c9de8f400b5bfa802eff Mon Sep 17 00:00:00 2001 From: Brooks Davis Date: Fri, 3 Sep 2021 19:30:23 +0100 Subject: [PATCH] mprotect.2: Remove legacy BSD text This text dates to the BSD 4.4 import and is misleading. The mprotect syscall acts on page granularity and breaks up mappings as required to do so. Note that with the addition of non-transparent superpages (aka largepages) the size of a page at a given address may vary. This commit does not attempt to address the lack of documentation of this feature. Sponsored by: DARPA Reviewed by: alc, mckusick, imp, kib, markj Differential Revision: https://reviews.freebsd.org/D31776 --- lib/libc/sys/mprotect.2 | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/lib/libc/sys/mprotect.2 b/lib/libc/sys/mprotect.2 index 0568343232b..5c024dd24d5 100644 --- a/lib/libc/sys/mprotect.2 +++ b/lib/libc/sys/mprotect.2 @@ -28,7 +28,7 @@ .\" @(#)mprotect.2 8.1 (Berkeley) 6/9/93 .\" $FreeBSD$ .\" -.Dd February 26, 2020 +.Dd September 3, 2021 .Dt MPROTECT 2 .Os .Sh NAME @@ -46,11 +46,6 @@ The system call changes the specified pages to have protection .Fa prot . -Not all implementations will guarantee protection on a page basis; -the granularity of protection changes may be as large as an entire region. -A region is the virtual address space defined by the start -and end addresses of a -.Vt "struct vm_map_entry" . .Pp Currently these protection bits are known, which can be combined, OR'd together: