linux.git/fs/splice.c, branch v2.6.18

[PATCH] splice: fix problems with sys_tee()

2006-07-10T09:00:01+00:00

Several issues noticed/fixed:

- We cannot reliably block in link_pipe() while holding both input and output
  mutexes. So do preparatory checks before locking down both mutexes and doing
  the link.

- The ipipe->nrbufs vs i check was bad, because we could have dropped the
  ipipe lock in-between. This causes us to potentially look at unknown
  buffers if we were racing with someone else reading this pipe.

Signed-off-by: Jens Axboe

[PATCH] splice: retrieve mapping after locking the page

2006-06-23T15:10:39+00:00

Otherwise we could be racing with truncate/mapping removal.

Problem found/fixed by Nick Piggin , logic rewritten
by me.

Signed-off-by: Jens Axboe

[PATCH] splice: redo page lookup if add_to_page_cache() returns -EEXIST

2006-05-04T04:55:12+00:00

This can happen quite easily, if several processes are trying to splice
the same file at the same time. It's not a failure, it just means someone
raced with us in allocating this file page. So just dump the allocated
page and relookup the original.

Signed-off-by: Jens Axboe

[PATCH] splice: rename remaining info variables to pipe

2006-05-04T04:55:12+00:00

Same thing was done in fs/pipe.c and most of fs/splice.c, but we had
a few missing still.

Signed-off-by: Jens Axboe

[PATCH] splice: LRU fixups

2006-05-04T04:55:12+00:00

Nick says that the current construct isn't safe. This goes back to the
original, but sets PIPE_BUF_FLAG_LRU on user pages as well as they all
seem to be on the LRU in the first place.

Signed-off-by: Jens Axboe

[PATCH] splice: fix unlocking of page on error ->prepare_write()

2006-05-04T04:55:12+00:00

Looking at generic_file_buffered_write(), we need to unlock_page() if
prepare write fails and it isn't due to racing with truncate().

Also trim the size if ->prepare_write() fails, if we have to.

Signed-off-by: Jens Axboe

[PATCH] vmsplice: restrict stealing a little more

2006-05-02T13:29:57+00:00

Apply the same rules as the anon pipe pages, only allow stealing
if no one else is using the page.

Signed-off-by: Jens Axboe

[PATCH] splice: fix page LRU accounting

2006-05-02T13:03:27+00:00

Currently we rely on the PIPE_BUF_FLAG_LRU flag being set correctly
to know whether we need to fiddle with page LRU state after stealing it,
however for some origins we just don't know if the page is on the LRU
list or not.

So remove PIPE_BUF_FLAG_LRU and do this check/add manually in pipe_to_file()
instead.

Signed-off-by: Jens Axboe

[PATCH] vmsplice: fix badly placed end paranthesis

2006-05-02T10:57:18+00:00

We need to use the minium of {len, PAGE_SIZE-off}, not {len, PAGE_SIZE}-off.
The latter doesn't make any sense, and could cause us to attempt negative
length transfers...

Signed-off-by: Jens Axboe

[PATCH] vmsplice: allow user to pass in gift pages

2006-05-01T18:02:33+00:00

If SPLICE_F_GIFT is set, the user is basically giving this pages away to
the kernel. That means we can steal them for eg page cache uses instead
of copying it.

The data must be properly page aligned and also a multiple of the page size
in length.

Signed-off-by: Jens Axboe