From: Johannes Berg <johannes@sipsolutions.net>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: [PATCH v2] dma-debug: print some unfreed allocations
Date: Wed, 11 May 2011 14:47:57 +0200 [thread overview]
Message-ID: <1305118077.3416.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1305052944.3544.8.camel@jlt3.sipsolutions.net>
From: Johannes Berg <johannes.berg@intel.com>
When a driver unbinds and still has allocations,
we print them out but there's no indication where
they came from. If stacktrace support is built
into the kernel, we can print out their traces.
Unfortunately, if you're unloading the module the
traces will be useless, but once you find such an
error you can manually unbind the device instead
to see where the allocations came from.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
v2: fix stupid error -- v1 printed almost everything *BUT* the device I wanted
lib/dma-debug.c | 48 ++++++++++++++++++++++++++++++++++++++----------
1 file changed, 38 insertions(+), 10 deletions(-)
--- a/lib/dma-debug.c 2011-05-11 12:44:22.000000000 +0200
+++ b/lib/dma-debug.c 2011-05-11 14:47:02.000000000 +0200
@@ -649,7 +649,9 @@ out_err:
return -ENOMEM;
}
-static int device_dma_allocations(struct device *dev)
+#define DMA_DEBUG_NUM_PRINT_UNFREED 10
+
+static void check_device_dma_allocations(struct device *dev)
{
struct dma_debug_entry *entry;
unsigned long flags;
@@ -666,27 +668,53 @@ static int device_dma_allocations(struct
spin_unlock(&dma_entry_hash[i].lock);
}
- local_irq_restore(flags);
+ if (count > 1) {
+ err_printk(dev, NULL, "DMA-API: device driver has pending "
+ "DMA allocations while released from device "
+ "[count=%d]\n", count);
+#ifdef CONFIG_STACKTRACE
+ count = 0;
+ /*
+ * If we have, print out some stack traces for the allocations.
+ * In case of module unload, the stack traces will be useless,
+ * but instead of unloading the module you can manually unbind
+ * the driver instead and get useful traces.
+ */
+ printk(KERN_WARNING "Showing traces for %d allocations:\n",
+ DMA_DEBUG_NUM_PRINT_UNFREED);
+
+ for (i = 0; i < HASH_SIZE; ++i) {
+ spin_lock(&dma_entry_hash[i].lock);
+ list_for_each_entry(entry, &dma_entry_hash[i].list,
+ list) {
+ if (entry->dev != dev)
+ continue;
+ count += 1;
+ if (count > DMA_DEBUG_NUM_PRINT_UNFREED)
+ break;
+ dump_entry_trace(entry);
+ }
+ spin_unlock(&dma_entry_hash[i].lock);
- return count;
+ if (count > DMA_DEBUG_NUM_PRINT_UNFREED)
+ break;
+ }
+#endif
+ }
+
+ local_irq_restore(flags);
}
static int dma_debug_device_change(struct notifier_block *nb, unsigned long action, void *data)
{
struct device *dev = data;
- int count;
if (global_disable)
return 0;
switch (action) {
case BUS_NOTIFY_UNBOUND_DRIVER:
- count = device_dma_allocations(dev);
- if (count == 0)
- break;
- err_printk(dev, NULL, "DMA-API: device driver has pending "
- "DMA allocations while released from device "
- "[count=%d]\n", count);
+ check_device_dma_allocations(dev);
break;
default:
break;
next prev parent reply other threads:[~2011-05-11 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 18:42 [PATCH] dma-debug: print some unfreed allocations Johannes Berg
2011-05-11 12:47 ` Johannes Berg [this message]
2011-05-16 11:00 ` [PATCH v2] " Roedel, Joerg
2011-05-18 22:48 ` Johannes Berg
2011-05-19 8:19 ` Roedel, Joerg
2011-05-20 16:36 ` [PATCH v3] " Johannes Berg
2011-05-23 12:35 ` Roedel, Joerg
2011-06-08 11:03 ` Johannes Berg
2011-06-08 12:16 ` Roedel, Joerg
2011-06-08 12:26 ` Johannes Berg
2011-06-08 12:37 ` Roedel, Joerg
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=1305118077.3416.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dwmw2@infradead.org \
--cc=joerg.roedel@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox