From: Lennart Poettering <lennart@poettering.net>
Date: Tue, 25 Jun 2024 10:46:19 +0000 (+0200)
Subject: mountpoint-util: clarify that EOVERFLOW is visible on nfs4/autofs mounts
X-Git-Tag: v257-rc1~1003^2~2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2ed5bd573807b937c2dff3dc915d5987c2a8f1c9;p=thirdparty%2Fsystemd.git

mountpoint-util: clarify that EOVERFLOW is visible on nfs4/autofs mounts
---

diff --git a/src/basic/mountpoint-util.c b/src/basic/mountpoint-util.c
index c9cf1bcdac3..2b05abfbfe4 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;