From: Jens Axboe <jens.axboe@oracle.com>
To: Christof Schmitt <christof.schmitt@de.ibm.com>
Cc: Tom Zanussi <zanussi@comcast.net>,
linux-btrace@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, wilder@us.ibm.com
Subject: Re: blktrace/relay/s390: Oops in subbuf_splice_actor
Date: Wed, 23 Apr 2008 07:08:50 +0000 [thread overview]
Message-ID: <20080423070850.GV12774@kernel.dk> (raw)
In-Reply-To: <20080423070605.GA5450@schmichrtp.de.ibm.com>
On Wed, Apr 23 2008, Christof Schmitt wrote:
> On Mon, Apr 07, 2008 at 11:23:07PM -0500, Tom Zanussi wrote:
> > > Dave, can you have a look at this? I can easily reproduce the problem
> > > on s390 Linux for testing and getting more debug information.
> > >
> >
> > Not sure anyone's still looking into this, but it doesn't look like an
> > s390 problem specifically. Apparently what happened was that some
> > internal changes to splice seem to have broken the relay splice_read
> > implementation. The above patch fixes part of the problem; the patch
> > below should fix the rest, and AFAICT it doesn't break anything else.
> >
> > Signed-off-by: Tom Zanussi <zanussi@comcast.net>
> >
> > diff --git a/fs/splice.c b/fs/splice.c
> > index a861bb3..068b210 100644
> > --- a/fs/splice.c
> > +++ b/fs/splice.c
> > @@ -1094,7 +1094,7 @@ long do_splice_direct(struct file *in, loff_t *ppos, struct file *out,
> >
> > ret = splice_direct_to_actor(in, &sd, direct_splice_actor);
> > if (ret > 0)
> > - *ppos += ret;
> > + *ppos = sd.pos;
> >
> > return ret;
> > }
> > diff --git a/kernel/relay.c b/kernel/relay.c
> > index d6204a4..dc873fb 100644
> > --- a/kernel/relay.c
> > +++ b/kernel/relay.c
> > @@ -1162,7 +1162,7 @@ static ssize_t relay_file_splice_read(struct file *in,
> > ret = 0;
> > spliced = 0;
> >
> > - while (len) {
> > + while (len && !spliced) {
> > ret = subbuf_splice_actor(in, ppos, pipe, len, flags, &nonpad_ret);
> > if (ret < 0)
> > break;
> >
> >
>
> Sorry for the late response and yes, our tests on s390 are still
> tracking the issue. I just ran a short test on 2.6.25 with the above
> patch applied. With this patch, blktrace client/server mode works
> again with the sendfile() call and returns valid data for blkparse.
>
> Thanks everybody for helping with this problem.
>
> Jens, will you pick up this patch for inclusion?
Certainly, thanks to Tom for providing this and you for testing!
--
Jens Axboe
next prev parent reply other threads:[~2008-04-23 7:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 8:43 blktrace/relay/s390: Oops in subbuf_splice_actor Christof Schmitt
2008-03-14 11:58 ` Jens Axboe
2008-03-14 13:05 ` Christof Schmitt
2008-03-14 13:10 ` Jens Axboe
2008-03-14 13:22 ` Christof Schmitt
2008-03-14 15:21 ` David Wilder
2008-03-14 16:28 ` Christof Schmitt
2008-03-17 8:08 ` Jens Axboe
2008-03-17 15:19 ` Christof Schmitt
2008-03-19 9:16 ` Christof Schmitt
2008-04-08 4:23 ` Tom Zanussi
2008-04-23 7:06 ` Christof Schmitt
2008-04-23 7:08 ` Jens Axboe [this message]
2008-04-23 7:45 ` Jens Axboe
2008-04-24 4:32 ` Tom Zanussi
2008-04-24 10:49 ` Jens Axboe
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=20080423070850.GV12774@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=christof.schmitt@de.ibm.com \
--cc=linux-btrace@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=wilder@us.ibm.com \
--cc=zanussi@comcast.net \
/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).