Lee Schermerhorn

Update the get_mempolicy(2) man page to add in the description of
the MPOL_F_MEMS_ALLOWED flag, added in 2.6.23.
mtk
Document additional EINVAL error that occurs is MPOL_F_MEMS_ALLOWED
is specified with either MPOL_F_ADDR or MPOL_F_NODE.

man2/get_mempolicy.2

@@ -63,6 +63,28 @@ the time of the call to
 using
 .BR set_mempolicy (2).
 
+If
+.I flags
+specifies
+.BR MPOL_F_MEMS_ALLOWED 
+(available since Linux 2.6.24), the
+.I mode
+argument is ignored and the set of nodes [memories] that the
+process is allowed to specify in subsequent calls to
+.BR mbind (2)
+or
+.BR set_mempolicy (2)
+[in the absense of any
+.IR "mode flags" ]
+is returned in
+.IR nodemask .
+It is not permitted to combine
+.B MPOL_F_MEMS_ALLOWED
+with either
+.B MPOL_F_ADDR
+or
+.BR MPOL_F_NODE .
+
 If
 .I flags
 specifies
@@ -192,6 +214,14 @@ but not
 .B MPOL_F_ADDR
 and the current process policy is not
 .BR MPOL_INTERLEAVE .
+Or,
+.I flags
+specified
+.B MPOL_F_MEMS_ALLOWED
+with either
+.B MPOL_F_ADDR
+or
+.BR MPOL_F_NODE .
 (And there are other
 .B EINVAL
 cases.)