[Bug 10191] New: dd with conv=fsync behaves unpredictable after dba0dc1999bb1e8bfe64607e2a9385cda361fcb7

bugzilla at busybox.net bugzilla at busybox.net
Tue Aug 8 21:18:34 UTC 2017


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

            Bug ID: 10191
           Summary: dd with conv=fsync behaves unpredictable after
                    dba0dc1999bb1e8bfe64607e2a9385cda361fcb7
           Product: Busybox
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Standard Compliance
          Assignee: unassigned at busybox.net
          Reporter: busybox at nmacleod.com
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Since:
https://git.busybox.net/busybox/commit/?id=dba0dc1999bb1e8bfe64607e2a9385cda361fcb7
(dd: call fsync() only once before exiting if conv=fsync is specified)

Writing a 100MB file using "dd bs=1M conv=fsync" will now only sync once rather
than 100 times (once every 1MB), which totally changes the behaviour of dd if
the progress of the dd is being monitored by another thread (for example, when
updating firmware and attempting to give the user feedback during the dd).

Can this change be reverted, or perhaps only perform one fsync if bs is NOT
specified?

I selected "Standard Compliance" for this component as this new behaviour makes
no sense to me. If I wanted to perform only a single sync after a dd, I'd
perform a "dd && sync", there's no need to change how conv=fsync works.

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


More information about the busybox-cvs mailing list