All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Bob Peterson <rpeterso@redhat.com>,
	ebiggers@kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v4] splice: only read in as much information as there is pipe buffer space
Date: Thu, 21 Nov 2019 17:20:54 -0800	[thread overview]
Message-ID: <20191122012054.GB2981917@magnolia> (raw)
In-Reply-To: <CAHc6FU57p6p7FXoYCe1AQNz54Fg2BZ5UsEW3BBUnhLaGq2SmsQ@mail.gmail.com>

On Thu, Nov 21, 2019 at 06:57:55PM +0100, Andreas Gruenbacher wrote:
> On Sat, Oct 19, 2019 at 6:14 PM Darrick J. Wong <darrick.wong@oracle.com> wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Andreas Grünbacher reports that on the two filesystems that support
> > iomap directio, it's possible for splice() to return -EAGAIN (instead of
> > a short splice) if the pipe being written to has less space available in
> > its pipe buffers than the length supplied by the calling process.
> >
> > Months ago we fixed splice_direct_to_actor to clamp the length of the
> > read request to the size of the splice pipe.  Do the same to do_splice.
> >
> > Fixes: 17614445576b6 ("splice: don't read more than available pipe space")
> > Reported-by: Andreas Grünbacher <andreas.gruenbacher@gmail.com>
> 
> Reviewed-by: Andreas Grünbacher <andreas.gruenbacher@gmail.com>

Cool, thanks.  I'll try to push this to Linus next week.

--D

> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > v4: use size_t for pipe_pages
> > ---
> >  fs/splice.c |   14 +++++++++++---
> >  1 file changed, 11 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/splice.c b/fs/splice.c
> > index 98412721f056..9b9b22d2215a 100644
> > --- a/fs/splice.c
> > +++ b/fs/splice.c
> > @@ -945,12 +945,13 @@ ssize_t splice_direct_to_actor(struct file *in, struct splice_desc *sd,
> >         WARN_ON_ONCE(pipe->nrbufs != 0);
> >
> >         while (len) {
> > +               size_t pipe_pages;
> >                 size_t read_len;
> >                 loff_t pos = sd->pos, prev_pos = pos;
> >
> >                 /* Don't try to read more the pipe has space for. */
> > -               read_len = min_t(size_t, len,
> > -                                (pipe->buffers - pipe->nrbufs) << PAGE_SHIFT);
> > +               pipe_pages = pipe->buffers - pipe->nrbufs;
> > +               read_len = min(len, pipe_pages << PAGE_SHIFT);
> >                 ret = do_splice_to(in, &pos, pipe, read_len, flags);
> >                 if (unlikely(ret <= 0))
> >                         goto out_release;
> > @@ -1180,8 +1181,15 @@ static long do_splice(struct file *in, loff_t __user *off_in,
> >
> >                 pipe_lock(opipe);
> >                 ret = wait_for_space(opipe, flags);
> > -               if (!ret)
> > +               if (!ret) {
> > +                       size_t pipe_pages;
> > +
> > +                       /* Don't try to read more the pipe has space for. */
> > +                       pipe_pages = opipe->buffers - opipe->nrbufs;
> > +                       len = min(len, pipe_pages << PAGE_SHIFT);
> > +
> >                         ret = do_splice_to(in, &offset, opipe, len, flags);
> > +               }
> >                 pipe_unlock(opipe);
> >                 if (ret > 0)
> >                         wakeup_pipe_readers(opipe);
> 

  reply	other threads:[~2019-11-22  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19 16:11 [PATCH v4] splice: only read in as much information as there is pipe buffer space Darrick J. Wong
2019-11-21 17:00 ` Darrick J. Wong
2019-11-21 17:57 ` Andreas Gruenbacher
2019-11-22  1:20   ` Darrick J. Wong [this message]
2019-11-22  1:25     ` Andreas Grünbacher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191122012054.GB2981917@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=agruenba@redhat.com \
    --cc=david@fromorbit.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=rpeterso@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.