linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Wilder <dwilder@us.ibm.com>
To: Christof Schmitt <christof.schmitt@de.ibm.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	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: Fri, 14 Mar 2008 15:21:03 +0000	[thread overview]
Message-ID: <47DA97DF.6010008@us.ibm.com> (raw)
In-Reply-To: <20080314132238.GA9815@schmichrtp.de.ibm.com>

Christof Schmitt wrote:
> On Fri, Mar 14, 2008 at 02:10:07PM +0100, Jens Axboe wrote:
>> On Fri, Mar 14 2008, Christof Schmitt wrote:
>>> On Fri, Mar 14, 2008 at 12:58:03PM +0100, Jens Axboe wrote:
>>>> That is indeed a bug, does this work for you?
>>>>
>>>> diff --git a/kernel/relay.c b/kernel/relay.c
>>>> index d080b9d..39d1fa8 100644
>>>> --- a/kernel/relay.c
>>>> +++ b/kernel/relay.c
>>>> @@ -1066,7 +1066,7 @@ static int subbuf_splice_actor(struct file *in,
>>>>  			       unsigned int flags,
>>>>  			       int *nonpad_ret)
>>>>  {
>>>> -	unsigned int pidx, poff, total_len, subbuf_pages, ret;
>>>> +	unsigned int pidx, poff, total_len, subbuf_pages, nr_pages, ret;
>>>>  	struct rchan_buf *rbuf = in->private_data;
>>>>  	unsigned int subbuf_size = rbuf->chan->subbuf_size;
>>>>  	uint64_t pos = (uint64_t) *ppos;
>>>> @@ -1098,7 +1098,9 @@ static int subbuf_splice_actor(struct file *in,
>>>>  	pidx = (read_start / PAGE_SIZE) % subbuf_pages;
>>>>  	poff = read_start & ~PAGE_MASK;
>>>>
>>>> -	for (total_len = 0; spd.nr_pages < subbuf_pages; spd.nr_pages++) {
>>>> +	nr_pages = min_t(unsigned int, subbuf_pages, PIPE_BUFFERS);
>>>> +
>>>> +	for (total_len = 0; spd.nr_pages < nr_pages; spd.nr_pages++) {
>>>>  		unsigned int this_len, this_end, private;
>>>>  		unsigned int cur_pos = read_start + total_len;
>>> With the patch, i can run dd and 'blktrace -h traceserver' without the
>>> oops. But the output from blktrace only contains only zeros and no
>>> usable data for blkparse. Using blktrace to write the data directly to
>>> disk, without using the blktrace server works. Is there anything i
>>> should look for to help debugging the problem?
>> We should probably get Tom in the loop, as he is the relay expert. I'll
>> make sure the above patch gets into 2.6.25, as it is definitely a bug
>> that needs fixing.
> 
> http://relayfs.sourceforge.net/contact.html mentions Tom Zanussi, but
> his email address seems to be no longer valid. I copy Dave Wilder
> here, since he is mentioned as relay maintainer on the web page.
> 
> Dave, can you have a look at this? I can easily reproduce the problem
> on s390 Linux for testing and getting more debug information.
> 
> Christof
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

I will take a look at the problem.
Any thing special about the test you are running I need to know?

  reply	other threads:[~2008-03-14 15:21 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 [this message]
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
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=47DA97DF.6010008@us.ibm.com \
    --to=dwilder@us.ibm.com \
    --cc=christof.schmitt@de.ibm.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=wilder@us.ibm.com \
    /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).