Skip to contentSkip to conversation

New: Possibly bad EBADF error description in fsync(2)

Bug 29972 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 3 messages Feb 26, 2011 – Dec 11, 2013 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=29972

Summary: Possibly bad EBADF error description in fsync(2)
Product: Documentation
Version: unspecified
Kernel Version: N/A
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
AssignedTo: documentation_man-pages-ztI5WcYan/[email protected]
ReportedBy: [email protected]
Regression: No

The man-page of fsync(2) has the next error description:
EBADF fd is not a valid file descriptor open for writing.

This man-page says nothing about if fsync(2) works correctly on a file descriptor open with O_RDONLY, but it seems to work without any problem. So that description induce to think that O_WRONLY or O_RDWR must be used.

The Open Group Base Specifications says nothing about in what mode the file must be open. And the EBADF error description also says nothing about not being open in writing mode
(http://pubs.opengroup.org/onlinepubs/009695399/functions/fsync.html).

In conclusion, as far as I know, the next code snippet is correct and seems to work correctly in my machine with regular files and directories:

    fd = open(path, O_RDONLY);
    fsync(fd);

So the EBADF error description in man pages from fsync(2) is confusing, maybe it should be something like:
EBADF fd is not a valid file descriptor.

I'm using Ubuntu 10.10 with Linux man-pages 3.24.

Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw

[Bug 29972] Possibly bad EBADF error description in fsync(2)

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=29972

Jorge Nerín <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Jorge Nerín <[email protected]> --- man-pages 3.51 fsync(2):

EBADF fd is not a valid open file descriptor.

I think this bug should be closed.

Signature · 5 lines
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

[Bug 29972] Possibly bad EBADF error description in fsync(2)

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=29972

Alan <alan-qBU/[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
                 CC|                            |alan-qBU/[email protected]
         Resolution|---                         |CODE_FIX
Signature · 6 lines
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html