Commit Message

Eric Dumazet a écrit :
> Eric Dumazet a écrit :>> Jason Gunthorpe a écrit :>>>> One way to handle this is to switch tcp_read() to use the underlying file O_NONBLOCK>>>> flag, as other socket operations do. And let SPLICE_F_NONBLOCK control the pipe output only.>> arg, this was tcp_splice_read() of course>>>>> Thanks Eric, this seems reasonable from my userspace perspective.>>>>>> I admit I don't understand why SPLICE_F_NONBLOCK exists, it seems very>>> un-unixy to have a syscall completely ignore the NONBLOCK flag of the>>> fd it is called on. Ie setting NONBLOCK on the pipe itself does>>> nothing when using splice..>>>>> Hmm, good question, I dont have the answer but I'll digg one.>>> > commit 29e350944fdc2dfca102500790d8ad6d6ff4f69d> splice: add SPLICE_F_NONBLOCK flag> > It doesn't make the splice itself necessarily nonblocking (because the> actual file descriptors that are spliced from/to may block unless they> have the O_NONBLOCK flag set), but it makes the splice pipe operations> nonblocking.> > Signed-off-by: Linus Torvalds <torvalds@osdl.org>> > > See Linus intention was pretty clear : O_NONBLOCK should be taken into account> by 'actual file that are spliced from/to', regardless of SPLICE_F_NONBLOCK flag>
I also found first submission of the patch from Octavian Purdila,
so credit should be given to Octavian as well.
http://lkml.indiana.edu/hypermail/linux/kernel/0807.2/0687.html
We could add Linus into the discussion if it can help to make progress on this point.
I personally stopped to use splice(tcp -> pipe) in my projects because it was not usable
in a reliable way.
Thanks
[PATCH] net: splice() from tcp to pipe should take into account O_NONBLOCK
tcp_splice_read() doesnt take into account socket's O_NONBLOCK flag
Before this patch :
splice(socket,0,pipe,0,128*1024,SPLICE_F_MOVE);
causes a random endless block (if pipe is full) and
splice(socket,0,pipe,0,128*1024,SPLICE_F_MOVE | SPLICE_F_NONBLOCK);
will return 0 immediately if the TCP buffer is empty.
User application has no way to instruct splice() that socket should be in blocking mode
but pipe in nonblock more.
Many projects cannot use splice(tcp -> pipe) because of this flaw.
http://git.samba.org/?p=samba.git;a=history;f=source3/lib/recvfile.c;h=ea0159642137390a0f7e57a123684e6e63e47581;hb=HEAD
http://lkml.indiana.edu/hypermail/linux/kernel/0807.2/0687.html
Linus introduced SPLICE_F_NONBLOCK in commit 29e350944fdc2dfca102500790d8ad6d6ff4f69d
(splice: add SPLICE_F_NONBLOCK flag )
It doesn't make the splice itself necessarily nonblocking (because the
actual file descriptors that are spliced from/to may block unless they
have the O_NONBLOCK flag set), but it makes the splice pipe operations
nonblocking.
Linus intention was clear : let SPLICE_F_NONBLOCK control the splice pipe mode only
This patch instruct tcp_splice_read() to use the underlying file O_NONBLOCK
flag, as other socket operations do.
Users will then call :
splice(socket,0,pipe,0,128*1024,SPLICE_F_MOVE | SPLICE_F_NONBLOCK );
to block on data coming from socket (if file is in blocking mode),
and not block on pipe output (to avoid deadlock)
First version of this patch was submitted by Octavian Purdila
Reported-by: Volker Lendecke <vl@samba.org>
Reported-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>Signed-off-by: Octavian Purdila <opurdila@ixiacom.com>
---
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html