public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: akpm@linux-foundation.org, joro@8bytes.org,
	linux-kernel@vger.kernel.org, shuahkhan@gmail.com
Subject: Re: [PATCH] dma-debug: enhance dma_debug_device_change() to check for mapping errors
Date: Tue, 12 Nov 2013 14:12:37 -0800	[thread overview]
Message-ID: <5282A7D5.7050406@intel.com> (raw)
In-Reply-To: <1384289478-9899-1-git-send-email-shuah.kh@samsung.com>

I think this might be overdoing the error checking by a bit.  I would
much rather have the DMA leaked error be visible than have it buried
under messages about the failure to check for DMA errors.  In my mind
the DMA buffer leak is much more serious than the failure to check for
mapping errors.

Thanks,

Alex


On 11/12/2013 12:51 PM, 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.
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> ---
>  lib/dma-debug.c | 23 +++++++++++++++--------
>  1 file changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/lib/dma-debug.c b/lib/dma-debug.c
> index d87a17a..6c17b90 100644
> --- a/lib/dma-debug.c
> +++ b/lib/dma-debug.c
> @@ -712,6 +712,19 @@ out_err:
>  	return -ENOMEM;
>  }
>  
> +static void check_dma_mapping_error(struct dma_debug_entry *ref,
> +				    struct dma_debug_entry *entry)
> +{
> +	if (entry->map_err_type == MAP_ERR_NOT_CHECKED) {
> +		err_printk(ref->dev, entry,
> +			   "DMA-API: device driver failed to check map error"
> +			   "[device address=0x%016llx] [size=%llu bytes] "
> +			   "[mapped as %s]",
> +			   ref->dev_addr, ref->size,
> +			   type2name[entry->type]);
> +	}
> +}
> +
>  static int device_dma_allocations(struct device *dev, struct dma_debug_entry **out_entry)
>  {
>  	struct dma_debug_entry *entry;
> @@ -724,6 +737,7 @@ 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) {
> +				check_dma_mapping_error(entry, entry);
>  				count += 1;
>  				*out_entry = entry;
>  			}
> @@ -928,14 +942,7 @@ static void check_unmap(struct dma_debug_entry *ref)
>  			   dir2name[ref->direction]);
>  	}
>  
> -	if (entry->map_err_type == MAP_ERR_NOT_CHECKED) {
> -		err_printk(ref->dev, entry,
> -			   "DMA-API: device driver failed to check map error"
> -			   "[device address=0x%016llx] [size=%llu bytes] "
> -			   "[mapped as %s]",
> -			   ref->dev_addr, ref->size,
> -			   type2name[entry->type]);
> -	}
> +	check_dma_mapping_error(ref, entry);
>  
>  	hash_bucket_del(entry);
>  	dma_entry_free(entry);


  reply	other threads:[~2013-11-12 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 20:51 [PATCH] dma-debug: enhance dma_debug_device_change() to check for mapping errors Shuah Khan
2013-11-12 22:12 ` Alexander Duyck [this message]
2013-11-12 22:20   ` Shuah Khan
2013-11-13  0:22     ` Alexander Duyck

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=5282A7D5.7050406@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=joro@8bytes.org \
    --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