From: linas@austin.ibm.com
To: paulus@au1.ibm.com, paulus@samba.org
Cc: linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: [PATCH] 2.6 PPC64 EEH unbalanced dev_get/put calls
Date: Fri, 2 Jul 2004 13:45:39 -0500 [thread overview]
Message-ID: <20040702134539.W21634@forte.austin.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
Hi Paul,
Please review and forward upstream the following patch.
This patch fixes some unbalanaced usage of pci_dev_get()/pci_dev_put() calls
in the eeh code. The old code had too many calls to dev_put, which could
cause memory structs to be freed prematurely, possibly leading to bad
bad pointer derefs in certain cases.
Cross-ref LTC bug 9283
Signed-off-by: Linas Vepstas <linas@linas.org>
--linas
[-- Attachment #2: eeh-unbalanced-dev-put-for-bkbits.patch --]
[-- Type: text/plain, Size: 925 bytes --]
===== arch/ppc64/kernel/eeh.c 1.20 vs edited =====
--- 1.20/arch/ppc64/kernel/eeh.c Thu Jul 1 17:27:56 2004
+++ edited/arch/ppc64/kernel/eeh.c Fri Jul 2 13:27:58 2004
@@ -207,7 +207,6 @@
if (!dn) {
printk(KERN_WARNING "PCI: no pci dn found for dev=%s %s\n",
pci_name(dev), pci_pretty_name(dev));
- pci_dev_put(dev);
return;
}
@@ -218,9 +217,9 @@
printk(KERN_INFO "PCI: skip building address cache for=%s %s\n",
pci_name(dev), pci_pretty_name(dev));
#endif
- pci_dev_put(dev);
return;
}
+ pci_dev_get(dev);
/* Walk resources on this device, poke them into the tree */
for (i = 0; i < DEVICE_COUNT_RESOURCE; i++) {
@@ -310,7 +309,6 @@
while ((dev = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
/* Ignore PCI bridges ( XXX why ??) */
if ((dev->class >> 16) == PCI_BASE_CLASS_BRIDGE) {
- pci_dev_put(dev);
continue;
}
pci_addr_cache_insert_device(dev);
next reply other threads:[~2004-07-02 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 18:45 linas [this message]
2004-07-03 5:13 ` Paul Mackerras
2004-07-06 16:18 ` linas
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=20040702134539.W21634@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=paulus@au1.ibm.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®