linux-kernel - Re: [PATCH] dma-debug: fix to not have dependency on get_dma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20121117120724.GR25742@8bytes.org>
Date:	Sat, 17 Nov 2012 13:07:24 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Shuah Khan <shuah.khan@...com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, kubakici@...pl,
	stern@...land.harvard.edu, Greg KH <gregkh@...uxfoundation.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Mark Salter <msalter@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>, shuahkhan@...il.com
Subject: Re: [PATCH] dma-debug: fix to not have dependency on get_dma_ops()
 interface

On Sat, Nov 03, 2012 at 05:00:07PM -0600, Shuah Khan wrote:
> dma-debug depends on get_dma_ops() interface. Several architectures
> do not define dma_ops and get_dma_ops(). When dma debug interfaces are
> used on an architecture (e.g: c6x) that doesn't define get_dmap_ops(),
> compilation fails. Changing dma-debug to call dma_mapping_error() instead
> of defining its own that calls get_dma_ops(), such that the internal use of
> dma_mapping_error() doesn't interfere with the debug_dma_mapping_error()
> interface's mapping error checks. Moving dma_mapping_error() checks in
> check_unmap() under the dma debug entry not found is sufficient to fix the
> problem.
> 
> Reference: https://lkml.org/lkml/2012/10/26/367
> 
> Signed-off-by: Shuah Khan <shuah.khan@...com>
> Reported-by: Mark Salter <msalter@...hat.com>

Sorry for the delay. I applied the patch to the dma-debug branch.


	Joerg


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/