aboutsummaryrefslogtreecommitdiffstats
path: root/net/kcm
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2016-09-17 20:44:45 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2016-10-03 20:40:55 -0400
commit8924feff66f35fe22ce77aafe3f21eb8e5cff881 (patch)
tree77d74a5edba4d1a30f484e0cffdecfcfcc113d79 /net/kcm
parentsplice: switch get_iovec_page_array() to iov_iter (diff)
downloadlinux-dev-8924feff66f35fe22ce77aafe3f21eb8e5cff881.tar.xz
linux-dev-8924feff66f35fe22ce77aafe3f21eb8e5cff881.zip
splice: lift pipe_lock out of splice_to_pipe()
* splice_to_pipe() stops at pipe overflow and does *not* take pipe_lock * ->splice_read() instances do the same * vmsplice_to_pipe() and do_splice() (ultimate callers of splice_to_pipe()) arrange for waiting, looping, etc. themselves. That should make pipe_lock the outermost one. Unfortunately, existing rules for the amount passed by vmsplice_to_pipe() and do_splice() are quite ugly _and_ userland code can be easily broken by changing those. It's not even "no more than the maximal capacity of this pipe" - it's "once we'd fed pipe->nr_buffers pages into the pipe, leave instead of waiting". Considering how poorly these rules are documented, let's try "wait for some space to appear, unless given SPLICE_F_NONBLOCK, then push into pipe and if we run into overflow, we are done". Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'net/kcm')
0 files changed, 0 insertions, 0 deletions