From f31ebeed31f783774a15217af7b1df44b3d4a0ae Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Tue, 4 Mar 2003 09:16:35 +0000 Subject: [PATCH] `df /some/mount-point' no longer hangs when an unrelated hard-mount is unavailable [__GLIBC__]: GNU libc's statvfs stats each mount point in /proc/mounts until it finds one with matching device number. This is unnecessary when the FILE argument *is* a mount point. No stat call is necessary in that case. So, disable the statvfs-testing code on systems with GNU libc. Reported by Andrei Gaponenko via Tim Waugh as RedHat bug# 84846. --- m4/fsusage.m4 | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/m4/fsusage.m4 b/m4/fsusage.m4 index 451a5cc8cc..ad63154ac4 100644 --- a/m4/fsusage.m4 +++ b/m4/fsusage.m4 @@ -1,4 +1,4 @@ -#serial 8 +#serial 9 # From fileutils/configure.in @@ -24,6 +24,11 @@ if test $ac_fsusage_space = no; then # SVR4 AC_CACHE_CHECK([for statvfs function (SVR4)], fu_cv_sys_stat_statvfs, [AC_TRY_LINK([#include +#ifdef __GLIBC__ +Do not use statvfs on systems with GNU libc, because that function stats +all preceding entries in /proc/mounts, and that makes df hang if even +one of the corresponding file systems is hard-mounted, but not available. +#endif #include ], [struct statvfs fsd; statvfs (0, &fsd);], fu_cv_sys_stat_statvfs=yes, -- 2.47.3