From: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
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: Fri, 22 Nov 2019 02:25:51 +0100 [thread overview]
Message-ID: <CAHpGcMJPoZUWiT0F2Vtsq-ZMWZpbbT3L-sKrDF8uueB1rQm_BA@mail.gmail.com> (raw)
In-Reply-To: <20191122012054.GB2981917@magnolia>
Am Fr., 22. Nov. 2019 um 02:24 Uhr schrieb Darrick J. Wong
<darrick.wong@oracle.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.
That would be great, thanks.
Andreas
prev parent reply other threads:[~2019-11-22 1:26 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
2019-11-22 1:25 ` Andreas Grünbacher [this message]
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=CAHpGcMJPoZUWiT0F2Vtsq-ZMWZpbbT3L-sKrDF8uueB1rQm_BA@mail.gmail.com \
--to=andreas.gruenbacher@gmail.com \
--cc=agruenba@redhat.com \
--cc=darrick.wong@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).