Clarify that vm_map_protect cannot upgrade max_protection
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:
parent
67056e3d08
commit
0cf197862d
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=349239
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user