Re: Bug: tests/fsync.c: don't check for fsync failure on invalid fd

[Paul Eggert]

On 03/13/13 14:04, Phillip Susi wrote:

> In a similar manner, it is *nice* that the debug libc's malloc can
> detect a double free

No, it's not similar.  POSIX says that a double free has
undefined behavior so an implementation can do what it likes.
In contrast, POSIX says that fsync (-1) must return -1
and set errno; an implementation is not free to do what it
likes, and cannot return 0.

I don't see this as a major issue.  libeatmydata is not a
porting target for gnulib or for GNU applications in general.
If it doesn't work, it doesn't work; it's no big deal.