Hello Alexander, On 1/31/22 19:32, Mathnerd314 wrote: > Hi, > > The POSIX standard says fsync(2) can return EINTR: > https://pubs.opengroup.org/onlinepubs/9699919799/ > > The man page does not: > https://man7.org/linux/man-pages/man2/fsync.2.html > > I think fsync can be interrupted by a signal on Linux, so this should > just be an oversight in the man page. > > At least, fsync on fuse seems be able to return EINTR: > https://github.com/torvalds/linux/blob/5367cf1c3ad02f7f14d79733814302a96cc97b96/fs/fuse/dev.c#L114 > > Actually there seem to be numerous error codes that can be returned > from all filesystem calls on fuse: ENOTCONN, ENOMEM, etc. But EINTR is > at least documented in the POSIX standard, whereas these others seem > really rare. But for full correctness I suppose these should be > documented as well. It would be quite an undertaking. > > -- Mathnerd314 (pseudonym) I got this report on linux-man@. Could you please confirm if there are any ERRORS that should be added to the fsync(2) manual page? Thanks, Alex Mathnerd314: Thanks for the report! It's useful to CC the relevant kernel developers when reporting non-trivial bugs such as this one. They know better than we do. :) Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
