From: Matthew Dobson <colpatch@us.ibm.com>
To: John Rose <johnrose@austin.ibm.com>
Cc: greg KH <gregkh@us.ibm.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6 probe.c "pcibus_class" Device Class, release function
Date: Tue, 03 Feb 2004 17:31:42 -0800 [thread overview]
Message-ID: <40204B7E.6030408@us.ibm.com> (raw)
In-Reply-To: 1075847619.28337.31.camel@verve
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
John Rose wrote:
> The function release_pcibus_dev() in probe.c defines the release procedure for
> device class pcibus_class. I want to suggest that this function be scrapped :)
>
> This release function is called in the code path of class_device_unregister().
> The pcibus_class devices aren't currently unregistered anywhere, from what I
> can tell, so this release function is currently unused. The runtime removal of
> PCI buses from logical partitions on PPC64 requires the unregistration of these
> class devices. The natural place to do this IMHO is in pci_remove_bus_device()
> in remove.c.
You're right that the class device isn't currently unregistered, and
that was an oversight in the patch I originally sent. Attatched is a
patch that remedies that situation. pci_remove_bus_device() *is* the
natural place to unregister the class_dev, and that's just what the
patch does.
> The problem is that this calls pci_destroy_dev(), which calls put() on the same
> "bridge" device that the release function does. This should only be done once
> in the course of removing a pci_bus, and I doubt that we want to change
> pci_destroy_dev(). The kfree() of the pci_bus struct is also done in both
> pci_remove_bus_device() and release_pcibus_dev().
Yep. The patch pulls the kfree() out of pci_remove_bus_device() and
calls class_device_unregister() in it's place. This will put() the
bridge device and free the pci_bus as needed. put() does need to be
called twice because the bridge device is get()'d twice: once when the
device is registered and once when it's bus device grabs a reference to it.
> So the only two operations in the release function are redundantly performed in
> the place where it makes sense to unregister. For these reasons, I think we
> should scrap the release function altogether and set that pointer in the struct
> class to NULL.
>
> Thoughts?
> John
Disagree, for the reasons above. ;) Patch attatched.
Cheers!
-Matt
[-- Attachment #2: pcibus_memleak-fix.patch --]
[-- Type: text/plain, Size: 495 bytes --]
diff -Nurp --exclude-from=/home/mcd/.dontdiff linux-2.6.2-rc3/drivers/pci/remove.c linux-2.6.2-rc3+pcibus_memleak-fix/drivers/pci/remove.c
--- linux-2.6.2-rc3/drivers/pci/remove.c Thu Jan 8 22:59:10 2004
+++ linux-2.6.2-rc3+pcibus_memleak-fix/drivers/pci/remove.c Tue Feb 3 17:17:30 2004
@@ -83,7 +83,7 @@ void pci_remove_bus_device(struct pci_de
list_del(&b->node);
spin_unlock(&pci_bus_lock);
- kfree(b);
+ class_device_unregister(&b->class_dev);
dev->subordinate = NULL;
}
next prev parent reply other threads:[~2004-02-04 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 22:33 2.6 probe.c "pcibus_class" Device Class, release function John Rose
2004-02-04 1:31 ` Matthew Dobson [this message]
2004-02-04 16:00 ` John Rose
2004-02-04 16:05 ` John Rose
2004-02-04 17:22 ` John Rose
2004-02-04 18:01 ` Greg KH
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=40204B7E.6030408@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=gregkh@us.ibm.com \
--cc=johnrose@austin.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.