From 5460546183de1022043ce424239579b4e330c276 Mon Sep 17 00:00:00 2001
From: emaste <emaste@FreeBSD.org>
Date: Thu, 20 Jun 2019 18:30:19 +0000
Subject: [PATCH] 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
---
 share/man/man9/vm_map_protect.9 | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/share/man/man9/vm_map_protect.9 b/share/man/man9/vm_map_protect.9
index 2c8b52f7e420..3bd615c710ff 100644
--- a/share/man/man9/vm_map_protect.9
+++ b/share/man/man9/vm_map_protect.9
@@ -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