[Bug 11806] New: df MOUNT_POINT hangs if any file system in /proc/self/mounts is unresponsive

bugzilla at busybox.net bugzilla at busybox.net
Thu Apr 25 14:38:14 UTC 2019


https://bugs.busybox.net/show_bug.cgi?id=11806

            Bug ID: 11806
           Summary: df MOUNT_POINT hangs if any file system in
                    /proc/self/mounts is unresponsive
           Product: Busybox
           Version: 1.29.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: nweeks at g.harvard.edu
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

When busybox df is invoked with a file operand that is a mount point, it still
appears to (per strace) read and sequentially stat every file systems listed in
/proc/mounts (/proc/self/mounts) until it finds an entry with a matching
st_dev. stat() (and thus df) can hang if one of the file systems in
/proc/self/mounts is, e.g., an unresponsive hard-mounted NFS file system.

df from GNU coreutils 8.22 (and earlier) has an optimization where if a df file
operand is a mount point, it will stat only that mount point, avoiding a hang
in the scenario where some other file system in /proc/self/mounts is in an
unresponsive state that would cause stat() to hang.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the busybox-cvs mailing list