d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify that vm_map_protect cannot upgrade max_protection

Browse Source 
It's implied by the man page's RETURN VALUES section, but be explicit in
the description that vm_map_protect can not set new protection bits that
are already in each entry's max_protection.

Reviewed by:	brooks
MFC After:	1 week
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D20709
This commit is contained in:
Ed Maste 2019-06-20 18:19:09 +00:00
parent 67056e3d08
commit 0cf197862d
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=349239
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
share/man/man9/vm_map_protect.9
View File

@ -25,7 +25,7 @@
.\"
.\" $FreeBSD$
.\"
.Dd July 19, 2003
.Dd June 20, 2019
.Dt VM_MAP_PROTECT 9
.Os
.Sh NAME
@ -51,6 +51,11 @@ within the map
.Fa map
to
.Fa new_prot .
The value specified by
.Fa new_prot
may not include any protection bits that are not set in
.Va max_protection
on every entry within the range.
.Pp
If
.Fa set_max