Skip to contentSkip to conversation

New: About splice returning 0

Bug 90911 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 3 messages Jan 7, 2015 – Mar 11, 2016 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=90911

Bug ID: 90911
Summary: About splice returning 0
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages-ztI5WcYan/[email protected]
Reporter: safinaskar-JGs/[email protected]
Regression: No

"man 2 splice" at Linux man-pages 2012-05-04 says:
"A return value of 0 means that there was no data to transfer, and it would not make sense to block, because there are no writers connected to the write end of the pipe referred to by fd_in."

This is very hard-to-understand sentence, so, please rewrite it somehow.

First of all, this is not clear from this sentence that it speaks about reading from pipe and not about writing. (At first I wrongly decided from this sentence that it speaks about writing to broken pipe without readers [despite of word "writers"]).

So, at least, please write so:
"If we read from pipe, then a return value of 0 means that there was no data to transfer, and it would not make sense to block, because there are no writers connected to the write end of the pipe referred to by fd_in."

Then, the actual truth is the following: splice returns 0 if and only if corresponding read would return 0, i. e. on EOF on input (and reading from pipe without writers is just a special case of EOF). And the sentence doesn't say anything about reading from files other that pipes. So, please, rewrite so:
"A return value of 0 means end of input. If input is pipe then this means that there was no data to transfer, and it would not make sense to block, because there are no writers connected to the write end of the pipe referred to by fd_in."

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

A message that is not in the archive (sent off-list or not yet received): bug-90911-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/

#2 lore raw

[Bug 90911] About splice returning 0

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

Michael Kerrisk <[email protected]> changed:

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

             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]
         Resolution|---                         |CODE_FIX

--- Comment #1 from Michael Kerrisk <[email protected]> --- (In reply to Askar Safin from comment #0)

Quoted 9 lines

Then, the actual truth is the following: splice returns 0 if and only if corresponding read would return 0, i. e. on EOF on input (and reading from pipe without writers is just a special case of EOF). And the sentence doesn't say anything about reading from files other that pipes. So, please, rewrite so:
"A return value of 0 means end of input. If input is pipe then this means that there was no data to transfer, and it would not make sense to block, because there are no writers connected to the write end of the pipe referred to by fd_in."

So I used that text, pretty much as you gave it. Thanks!

Cheers,

Michael

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
#3 lore raw

[Bug 90911] About splice returning 0

In reply to a message not in the archive

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

--- Comment #2 from Askar Safin <safinaskar-JGs/[email protected]> --- Thanks :)

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