linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@sgi.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Latest bk kernel does not properly free PCI IO & MEM allocations
Date: Thu, 10 Mar 2005 18:16:52 +0000	[thread overview]
Message-ID: <42308F14.3020501@sgi.com> (raw)
In-Reply-To: <422F42A9.7050009@sgi.com>



Greg KH wrote:

>>I tracked down the issue to the following:
>>
>>When pci_remove_bus_device is called on the device in the slot (should be a 
>>safe thing to do) both the pci_driver remove function for a device and the 
>>function pci_free_resources are called.
>>
>>In the case of the QLA2x00 driver, the driver's remove function calls
>>pci_release_regions.  This function releases the IO & MEM allocs for the pci
>>device and kfree's them.
>>
>>As previously mentioned, pci_free_resources is called.  This function 
>>attempts to use and free IO & MEM allocs for the pci device.
>>    
>>
>
>Where does it attempt to use it?  I see a loop to free the resources,
>not anything else.
>
>  
>
Sorry -- I confused you.  I meant "use and then free" in that it uses 
kfree'd memory and then attempts to free the resources. 

>Also, if you enable slab debugging, does this always occur?
>  
>
Haven't tried that ... I'll give it a shot and report back to the list.

>And, this should be brought up on the linux-pci mailing list, not the
>hotplug list.
>
>  
>
I'll defer to your judgement on that :)  Given the code paths above it 
seemed to be a hotplug issue to me :)

>thanks,
>
>  
>
Thanks for your reply -- I'll turn on slab debug and see what happens...

>greg k-h
>
>
>  
>
P.

>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
>_______________________________________________
>Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
>Linux-hotplug-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
>
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-03-10 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 18:38 Latest bk kernel does not properly free PCI IO & MEM allocations Prarit Bhargava
2005-03-10 15:07 ` Prarit Bhargava
2005-03-10 17:17 ` Greg KH
2005-03-10 18:16 ` Prarit Bhargava [this message]
2005-03-10 18:50 ` Prarit Bhargava
2005-03-10 23:23 ` Greg KH
2005-03-11 21:30 ` Prarit Bhargava
2005-03-12  7:38 ` Greg KH
2005-03-12 17:04 ` prarit
2005-03-13  0:49 ` Re: Latest bk kernel does not properly free PCI IO & MEM prarit
2005-03-15  6:11 ` Re: Latest bk kernel does not properly free PCI IO & MEM allocations Rajesh Shah
2005-03-15 12:55 ` Prarit Bhargava

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=42308F14.3020501@sgi.com \
    --to=prarit@sgi.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).