[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#9141: fdatasync module proposal

From: Eric Blake
Subject: bug#9141: fdatasync module proposal
Date: Fri, 16 Sep 2011 12:28:28 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110831 Fedora/3.1.12-2.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.12

On 07/22/2011 03:13 PM, Paul Eggert wrote:
Surely coreutils is not the only program that will have problems
with fdatasync on Mac OS.  How about the following gnulib patches?

  Portability problems fixed by Gnulib:
+This function is present but undeclared and ineffective on some platforms:
+MacOS X 10.7

Do we know this to be the case, or are you just going off of web searches? For example:


"Although the fdatasync function is not referenced in the standard includes (hence the warning), it is present as a syscall:
/usr/include/sys/syscall.h:#define      SYS_fdatasync      187
Moreover, a fdatasync symbol is available through libSystem"

"Compiling just fine doesn't necessarily mean thatt qemu will run fine and do what we want it to do. But in this case it may: i took a look at the XNU sources (I didn't think about this solution first, I forgot it was open source...) and fdatasync appears to be implemented."

That is, on MacOS 10.7, must we implement fdatasync via the heavier fsync, or can we merely add the declaration and let the syscall do its job?

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]