public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amit Patel <patelamitv@yahoo.com>
To: Nick Piggin <piggin@cyberone.com.au>, Amit Patel <patelamitv@YAHOO.COM>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: as_arq scheduler alloc with 2.6.0-test8-mm1
Date: Tue, 28 Oct 2003 17:45:17 -0800 (PST)	[thread overview]
Message-ID: <20031029014517.60577.qmail@web13012.mail.yahoo.com> (raw)
In-Reply-To: <3F9DABE6.7050501@cyberone.com.au>

Hi 

After doing some printk debugging looks like for each
block device we allocate elevator structure. But
during cleanup the elevator->elevator_data is never
freed. In printk I put printk in as-iosched.c:as_alloc
where I see elevator_data is allocated from as_arq
pool and it should have been freed as a part of block
device cleanup through elevator_release function. I
never see it coming to elevatore_release function. 

I will try to walk through code some more and see if I
can figure out who was supposed to call
elevator_release as part of cleanup. Let me know if I
am going on wrong track here.

Thanks
Amit
--- Nick Piggin <piggin@cyberone.com.au> wrote:
> 
> 
> Mr Amit Patel wrote:
> 
> >Hi Andrew,
> >
> >The qlogic driver is for Fibre Channel HBA QLA2342.
> >This is a beta driver which is part of the mjb1
> patch
> >against 2.6.0-test8. As a part of driver insmod,
> >driver tries to find fiber channel device and maps
> it
> >to scsi block device. Actually I don't have any
> fibre
> >channel target attached, so driver does not find
> any
> >scsi devices and discovery finishes without adding
> any
> >block device. 
> >
> >I am trying to go through driver scsi_scan process
> and
> >see when does actual allocation from as_arq
> happens.
> >But for some reason after going to kgdb I get
> SIGEMT
> >and I cannot debug further. What is causing SIGEMT
> >cause after doing some search looks like its
> actually
> >SIGUSR but linux treats it as SIGEMT. Is there any
> way
> >to prevent SIGEMT when I want to use kgdb ? 
> >
> >Thanks for your help,
> >
> 
> Hi Amit,
> 
> I'm a little bit busy to look at this now, however
> someone
> is looking into all these refcounting problems.
> 
> If you would like to narrow it down a bit, check
> that the
> request queues that are allocated are all released
> when the
> driver is unloaded (drivers/block/ll_rw_blk.c
> blk_alloc_queue
> and blk_cleanup_queue). Just stick a couple of
> printks there
> if your debugger isn't working.
> 
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

  reply	other threads:[~2003-10-29  1:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26  9:54 as_arq scheduler alloc with 2.6.0-test8-mm1 Mr Amit Patel
2003-10-26 11:41 ` Andrew Morton
2003-10-26 18:03   ` Mr Amit Patel
2003-10-27 17:59   ` Mr Amit Patel
2003-10-27 21:38     ` Andrew Morton
2003-10-27 23:36     ` Nick Piggin
2003-10-29  1:45       ` Amit Patel [this message]
     [not found] <3F9F2928.7030704@cyberone.com.au>
2003-10-29  4:34 ` Amit Patel
2003-10-29  4:48   ` Nick Piggin

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=20031029014517.60577.qmail@web13012.mail.yahoo.com \
    --to=patelamitv@yahoo.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.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