public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc2-bk7 - Badness in cfq_put_request at drivers/block/cfq-iosched.c:1402
Date: Wed, 24 Nov 2004 14:40:38 +0100	[thread overview]
Message-ID: <20041124134038.GF13847@suse.de> (raw)
In-Reply-To: <002e01c4d22a$f426f630$0201a8c0@hawk>

On Wed, Nov 24 2004, Christopher S. Aker wrote:
> > On Wed, Nov 24 2004, Jens Axboe wrote:
> > > On Wed, Nov 24 2004, Christopher S. Aker wrote:
> > > > Badness in cfq_put_request at drivers/block/cfq-iosched.c:1402
> > > >  [<c025eed4>] cfq_put_request+0xcc/0x119
> > > >  [<c0252520>] elv_put_request+0x25/0x27
> > > >  [<c02553a5>] __blk_put_request+0x66/0xab
> > > >  [<c0256647>] end_that_request_last+0x6a/0x10b
> > > >  [<c029d836>] scsi_end_request+0xbf/0xe6
> > > >  [<c029db11>] scsi_io_completion+0x117/0x4b6
> > > >  [<c029b2e2>] scsi_delete_timer+0x1a/0x66
> > > >  [<c02a9290>] sd_rw_intr+0x89/0x30f
> > > >  [<c0114472>] rebalance_tick+0xac/0xbb
> > > >  [<c0298e8a>] scsi_finish_command+0x85/0xd9
> > > >  [<c0298d9d>] scsi_softirq+0xb7/0xdd
> > > >  [<c011cba7>] __do_softirq+0xb7/0xc6
> > > >  [<c011cbe3>] do_softirq+0x2d/0x2f
> > > >  [<c01046b6>] do_IRQ+0x1e/0x24
> > > >  [<c0102db2>] common_interrupt+0x1a/0x20
> > > >  [<c01005da>] mwait_idle+0x31/0x48
> > > >  [<c01005a0>] cpu_idle+0x33/0x3c
> > > >  [<c046aa49>] start_kernel+0x175/0x1b1
> > > >  [<c046a4bd>] unknown_bootoption+0x0/0x1ab
> > > 
> > > It's a known issue, just not fixed yet... You can ignore the warning,
> > > cfq recovers the condition.
> > 
> > Is this an SMP machine, btw?
> 
> Yep.

Can you try this simple check to see if it triggers anything?

===== cfq-iosched.c 1.13 vs edited =====
--- 1.13/drivers/block/cfq-iosched.c	2004-10-30 01:35:21 +02:00
+++ edited/cfq-iosched.c	2004-11-24 14:40:13 +01:00
@@ -1389,6 +1389,8 @@
 	struct cfq_data *cfqd = q->elevator->elevator_data;
 	struct cfq_rq *crq = RQ_DATA(rq);
 
+	WARN_ON(!spin_is_locked(q->queue_lock));
+
 	if (crq) {
 		struct cfq_queue *cfqq = crq->cfq_queue;
 

-- 
Jens Axboe


  reply	other threads:[~2004-11-24 17:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24  7:24 2.6.10-rc2-bk7 - Badness in cfq_put_request at drivers/block/cfq-iosched.c:1402 Christopher S. Aker
2004-11-24 13:01 ` Jens Axboe
2004-11-24 13:24   ` Jens Axboe
2004-11-24 13:38     ` Christopher S. Aker
2004-11-24 13:40       ` Jens Axboe [this message]
2004-11-24 19:29         ` Christopher S. Aker
2004-11-25 18:43           ` Jens Axboe
2004-11-26  7:43             ` Jens Axboe
2004-11-26  8:07               ` 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=20041124134038.GF13847@suse.de \
    --to=axboe@suse.de \
    --cc=caker@theshore.net \
    --cc=linux-kernel@vger.kernel.org \
    /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