public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Andre Noll <maan@systemlinux.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic
Date: Thu, 8 Mar 2007 11:35:08 +0100	[thread overview]
Message-ID: <20070308103508.GD9671@kernel.dk> (raw)
In-Reply-To: <20070308102936.GD4252@skl-net.de>

On Thu, Mar 08 2007, Andre Noll wrote:
> On 10:36, Jens Axboe wrote:
> > - Edit .config and set CONFIG_DEBUG_INFO=y (near the bottom)
> > - make oldconfig
> > - rm block/cfq-iosched.o
> > - make block/cfq-iosched.o
> > - gdb block/cfq-iosched.o
> > 
> > (gdb) l *cfq_dispatch_insert+0x28
> > 
> > and see what that says. Should not take you more than a minute or so,
> > would appreciate it!
> 
> No problem, here we go:
> 
> # gdb block/cfq-iosched.o
> GNU gdb 6.4-debian
> Copyright 2005 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
> 
> (gdb) l *cfq_dispatch_insert+0x28
> 0xcf8 is in cfq_dispatch_insert (block/cfq-iosched.c:865).
> 860     }
> 861
> 862     static void cfq_dispatch_insert(request_queue_t *q, struct request *rq)
> 863     {
> 864             struct cfq_data *cfqd = q->elevator->elevator_data;
> 865             struct cfq_queue *cfqq = RQ_CFQQ(rq);
> 866
> 867             cfq_remove_request(rq);
> 868             cfqq->on_dispatch[rq_is_sync(rq)]++;
> 869             elv_dispatch_sort(q, rq);

Ok, so it's ->next_rq being NULL or invalid. Similar to the report from
Dan last week, that's a bit worrisome. I'll have to look further into
that.

-- 
Jens Axboe


      reply	other threads:[~2007-03-08 10:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 13:31 qla2xxx BUG: workqueue leaked lock or atomic Andre Noll
2007-02-26 18:26 ` Andrew Vasquez
2007-02-27 10:11   ` Andre Noll
2007-02-27 14:35     ` Andre Noll
2007-02-27 18:51     ` Andrew Vasquez
2007-02-28 15:18       ` Andre Noll
2007-02-28 15:37         ` Andre Noll
2007-03-07  4:39           ` Andrew Morton
2007-03-07 17:09             ` Andre Noll
2007-03-07 19:45               ` Andrew Morton
2007-03-07 20:05                 ` Mingming Cao
2007-03-09  9:36                   ` Andre Noll
2007-03-07 18:46           ` Jens Axboe
2007-03-08  8:52             ` Andre Noll
2007-03-08  9:02               ` Jens Axboe
2007-03-08  9:33                 ` Andre Noll
2007-03-08  9:36                   ` Jens Axboe
2007-03-08 10:29                     ` Andre Noll
2007-03-08 10:35                       ` Jens Axboe [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=20070308103508.GD9671@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maan@systemlinux.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