Author: emaste
Date: Thu Jun 20 18:19:09 2019
New Revision: 349239
URL: https://svnweb.freebsd.org/changeset/base/349239

Log:
  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

Modified:
  head/share/man/man9/vm_map_protect.9

Modified: head/share/man/man9/vm_map_protect.9
==============================================================================
--- head/share/man/man9/vm_map_protect.9        Thu Jun 20 17:08:21 2019        
(r349238)
+++ head/share/man/man9/vm_map_protect.9        Thu Jun 20 18:19:09 2019        
(r349239)
@@ -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
_______________________________________________
svn-src-head@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"

Reply via email to