summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2024-06-25 12:46:19 +0200
committerLennart Poettering <lennart@poettering.net>2024-07-01 15:45:15 +0200
commit2ed5bd573807b937c2dff3dc915d5987c2a8f1c9 (patch)
treeaf7d7a74fb1f5e8e3e9f33c502134c4fa29ad73a
parentmountpoint-util: use the FID stuff for detecting the root of mounts (diff)
downloadsystemd-2ed5bd573807b937c2dff3dc915d5987c2a8f1c9.tar.xz
systemd-2ed5bd573807b937c2dff3dc915d5987c2a8f1c9.zip
mountpoint-util: clarify that EOVERFLOW is visible on nfs4/autofs mounts
-rw-r--r--src/basic/mountpoint-util.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/basic/mountpoint-util.c b/src/basic/mountpoint-util.c
index c9cf1bcdac..2b05abfbfe 100644
--- a/src/basic/mountpoint-util.c
+++ b/src/basic/mountpoint-util.c
@@ -106,9 +106,9 @@ int name_to_handle_at_loop(
return 0;
}
- /* If name_to_handle_at() didn't increase the byte size, then this EOVERFLOW is caused by something
- * else (apparently EOVERFLOW is returned for untriggered nfs4 mounts sometimes), not by the too small
- * buffer. In that case propagate EOVERFLOW */
+ /* If name_to_handle_at() didn't increase the byte size, then this EOVERFLOW is caused by
+ * something else (apparently EOVERFLOW is returned for untriggered nfs4 autofs mounts
+ * sometimes), not by the too small buffer. In that case propagate EOVERFLOW */
if (h->handle_bytes <= n)
return -EOVERFLOW;