linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: prarit (prarit@prarit.com) <prarit@verizon.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Re: Latest bk kernel does not properly free PCI IO & MEM
Date: Sun, 13 Mar 2005 00:49:42 +0000	[thread overview]
Message-ID: <0ID9002ARMAUPH11@vms048.mailsrvcs.net> (raw)
In-Reply-To: <422F42A9.7050009@sgi.com>

> So running a UP kernel on your box doesn't cause any problems?

Gee .. I haven't actually tried it :).  That's probably a 
good test to run ... I'll try that first thing on 
Monday.

> > Additionally, I've seen people using PCI Hotplug in the field. 
> > Typically when removing a card sysadmins tend to quiesce the system
> > before removal.  That makes #4 just that much less likely to occur.
> 
> It's usually a good idea to do this :)
> 

In some sense, yes.  I would argue that it's not a 
PCI HotPlug issue, but a driver issue -- most of the
drivers out there don't pay a lot of attention to the
stability of the driver remove function :(

I've seen all sorts of things in removes that are done
wrong -- from not terminating timers, to not quiecing
queues, to not properly kfree'ing memory.

Qlogic drivers are especially bad :) ... That's why
I hesitate to test with them in the system but in this
case it was what was available to me.

> > :) :)  Want the long explanation? :) :)
> 
> Sure...
> 

I'll go back to work and pull out the oops' etc.

> Anyway, I'll add the basic, NULL out the pointer and check for it patch
> to the tree soon, so that your oops should not happen anymore.

Thanks Greg :)  I've tested with that patch and it
seems better.  IMO though, we still have a glitch
in PCI.  I'm not convinced that it should be calling
pci_free_resources at all.  

> 
> thanks,
> 
> greg k-h
> 

Thanks,

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

  parent reply	other threads:[~2005-03-13  0:49 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
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 ` prarit [this message]
2005-03-15  6:11 ` 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=0ID9002ARMAUPH11@vms048.mailsrvcs.net \
    --to=prarit@verizon.net \
    --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).