linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [CFQ/OOPS]  rb_erase with April 9 next tree
Date: Fri, 10 Apr 2009 12:10:02 +0530	[thread overview]
Message-ID: <49DEE9C2.1040500@in.ibm.com> (raw)
In-Reply-To: <20090409174420.GG5178@kernel.dk>

Jens Axboe wrote:
>
> Can you see if this fixes it for you?
>
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index e01b103..64de5c0 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -1654,6 +1654,7 @@ retry:
>  		}
>
>  		RB_CLEAR_NODE(&cfqq->rb_node);
> +		RB_CLEAR_NODE(&cfqq->p_node);
>  		INIT_LIST_HEAD(&cfqq->fifo);
>
>  		atomic_set(&cfqq->ref, 0);
>   
Yes. The above patch fixed this oops. Thanks

Regards
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------


  reply	other threads:[~2009-04-10  6:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  6:33 linux-next: Tree for April 9 Stephen Rothwell
2009-04-09 10:08 ` Next April 9 : x86 allmodconfig media/video/cx88 build break Sachin Sant
2009-04-09 10:28   ` Mauro Carvalho Chehab
2009-04-09 15:51 ` [CFQ/OOPS] rb_erase with April 9 next tree Sachin Sant
2009-04-09 17:29   ` Jens Axboe
2009-04-09 17:44     ` Jens Axboe
2009-04-10  6:40       ` Sachin Sant [this message]
2009-04-11  6:11 ` linux-next: Tree for April 9 Andrew Morton
2009-04-11 11:09   ` Mauro Carvalho Chehab
2009-04-11 12:05     ` Stephen Rothwell

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=49DEE9C2.1040500@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).