[PATCH v2 2/2] man/man2/statmount.2: Fix incorrect naming of STATMOUNT_MNT_{UID,GID}MAP flags

Bhavik Sachdev <[email protected]> Thu, 19 Mar 2026 12:39:12 +0530
Newsgroups dev.linux.lists.criu,org.kernel.vger.linux-man
Message-ID <4f6135c8b84b8b291a7145a72f216e77f8cf0103.1773904035.git.b.sachdev1904@gmail.com>
STATMOUNT_UIDMAP is actually STATMOUNT_MNT_UIDMAP and STATMOUNT_GIDMAP
is STATMOUNT_MNT_GIDMAP.

Fixes: 9968ead5 (2026-03-05; "man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP}")
Signed-off-by: Bhavik Sachdev <[email protected]>
---
Hey Alex!

Found another mistake while replying to your comments!

Thanks,
Bhavik

 man/man2/statmount.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man/man2/statmount.2 b/man/man2/statmount.2
index 78b6e9be..b6d9dc2a 100644
--- a/man/man2/statmount.2
+++ b/man/man2/statmount.2
@@ -355,7 +355,7 @@ .SS The returned information
 The number of uid mappings applied on the mount.
 If
 .I smbuf.mask
-has STATMOUNT_UIDMAP set and this field is 0,
+has STATMOUNT_MNT_UIDMAP set and this field is 0,
 then uid mappings applied on the mount
 cannot be resolved in the user namespace of the caller.
 .TP
@@ -372,7 +372,7 @@ .SS The returned information
 The number of gid mappings applied on the mount.
 If
 .I smbuf.mask
-has STATMOUNT_GIDMAP set and this field is 0,
+has STATMOUNT_MNT_GIDMAP set and this field is 0,
 then gid mappings applied on the mount
 cannot be resolved in the user namespace of the caller.
 .TP
-- 
2.53.0