Date: Thu, 20 Jun 2019 18:30:19 +0000 (UTC) From: Ed Maste <emaste@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r349241 - head/share/man/man9 Message-ID: <201906201830.x5KIUJXe052103@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: emaste Date: Thu Jun 20 18:30:19 2019 New Revision: 349241 URL: https://svnweb.freebsd.org/changeset/base/349241 Log: Clarify vm_map_protect max_protection downgrade As reported in review D20709 by brooks calling vm_map_protect to set a new max_protection value downgrades existing mappings if necessary (as opposed to returning an error). Reported by: brooks MFC after: 1 week Sponsored by: The FreeBSD Foundation 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 18:24:16 2019 (r349240) +++ head/share/man/man9/vm_map_protect.9 Thu Jun 20 18:30:19 2019 (r349241) @@ -64,7 +64,12 @@ is TRUE, is treated as the new .Va max_protection setting for each underlying entry. -Otherwise, only the +Protection bits not included +.Fa new_prot +will be cleared from existing entries. +If +.Fa set_max +is FALSE only the .Va protection field is affected. .Pp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906201830.x5KIUJXe052103>