On Sun, Sep 18, 2016 at 01:12:21PM -0700, Linus Torvalds wrote:
> So if the splice code ends up being confused by "this is not just
> inside a single page", then the splice code is buggy, I think.
>
> Why would splice_write() cases be confused anyway? A filesystem needs
> to be able to handle the case of "this needs to be split" regardless,
> since even if the source buffer were to fit in a page, the offset
> might obviously mean that the target won't fit in a page.
What worries me is iov_iter_get_pages() and friends. The calling conventions
are
size = iov_iter_get_pages(iter, pages, maxlen, maxpages, &start);
They are convenient enough for most of the callers - we fill an array of
pages, the first (and only in bvec case) one having start bytes skipped.
The thing is, the calculation of the number of pages returned is broken
in this case; normally it's ROUND_DIV_UP(start + n, PAGE_SIZE). That,
of course, gets broken even by the offset being large enough. We don't
have that many users of that thing (and iov_iter_get_pages_alloc()), but
it'll need careful review. What's more, looking at those shows other
fun issues:
sg_init_table(sgl->sg, npages + 1);
for (i = 0, len = n; i < npages; i++) {
int plen = min_t(int, len, PAGE_SIZE - off);
sg_set_page(sgl->sg + i, sgl->pages[i], plen, off);
and that'll instantly blow up, due to PAGE_SIZE - off possibly becoming
negative. That's af_alg_make_sg(), and it shouldn't see anything
coming from pipe buffers (right now the only way for that to happen is
iter_file_splice_write()), but the things like e.g. dio_refill_pages()
might, and they also get seriously confused by that. Worse, some of those
callers have calling conventions that have similar problems of their own.
At the moment there are 11 callers (10 in mainline; one more added in
conversion of vmsplice_to_pipe() to new pipe locking, but it's irrelevant
anyway - it gets fed an iovec-backed iov_iter). I'm looking through those
right now, hopefully will come up with something sane...
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
