From: Joerg Roedel <joro@8bytes.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: akpm@linux-foundation.org, alexander.h.duyck@intel.com,
linux-kernel@vger.kernel.org, shuahkhan@gmail.com
Subject: Re: [PATCH v2] dma-debug: enhance dma_debug_device_change() to check for mapping errors
Date: Mon, 30 Dec 2013 15:15:12 +0100 [thread overview]
Message-ID: <20131230141511.GC2799@8bytes.org> (raw)
In-Reply-To: <1384376168-2148-1-git-send-email-shuah.kh@samsung.com>
On Wed, Nov 13, 2013 at 01:56:08PM -0700, Shuah Khan wrote:
> dma-debug checks to verify if driver validated the address returned by
> dma mapping routines when driver does unmap. If a driver doesn't call
> unmap, failure to check mapping errors isn't detected and reported.
>
> Enhancing existing bus notifier_call dma_debug_device_change() to check
> for mapping errors at the same time it detects leaked dma buffers for
> BUS_NOTIFY_UNBOUND_DRIVER event. It scans for mapping errors and if any
> found, prints one warning message that includes mapping error count.
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> ---
> lib/dma-debug.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/lib/dma-debug.c b/lib/dma-debug.c
> index d87a17a..e34865e 100644
> --- a/lib/dma-debug.c
> +++ b/lib/dma-debug.c
> @@ -717,6 +717,7 @@ static int device_dma_allocations(struct device *dev, struct dma_debug_entry **o
> struct dma_debug_entry *entry;
> unsigned long flags;
> int count = 0, i;
> + int map_err_cnt = 0;
>
> local_irq_save(flags);
>
> @@ -724,6 +725,8 @@ static int device_dma_allocations(struct device *dev, struct dma_debug_entry **o
> spin_lock(&dma_entry_hash[i].lock);
> list_for_each_entry(entry, &dma_entry_hash[i].list, list) {
> if (entry->dev == dev) {
> + if (entry->map_err_type == MAP_ERR_NOT_CHECKED)
> + map_err_cnt += 1;
> count += 1;
> *out_entry = entry;
I think it is better to check for this in a seperate function and use
err_printk instead of dev_warn in the end to print the errors.
The new function can then be called in the dma_debug_device_change
callback like device_dma_allocations is.
Joerg
next prev parent reply other threads:[~2013-12-30 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:56 Shuah Khan
2013-12-30 14:15 ` Joerg Roedel [this message]
2014-01-03 18:26 ` Shuah Khan
2014-01-07 14:26 ` Joerg Roedel
2014-01-07 15:00 ` Shuah Khan
2014-01-07 15:12 ` Joerg Roedel
2014-01-07 17:22 ` Shuah Khan
2014-01-11 0:25 ` Shuah Khan
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=20131230141511.GC2799@8bytes.org \
--to=joro@8bytes.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah.kh@samsung.com \
--cc=shuahkhan@gmail.com \
/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
Powered by JetHome