linux-kernel - [PATCH] Fix the issue of fsldma driver's VIRT_TO

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>] [day] [month] [year] [list]

Message-Id: <119503706990-git-send-email-wei.zhang@freescale.com>
Date:	Wed, 14 Nov 2007 18:44:29 +0800
From:	Zhang Wei <wei.zhang@...escale.com>
To:	akpm@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, olof@...om.net,
	Zhang Wei <wei.zhang@...escale.com>
Subject: [PATCH] Fix the issue of fsldma driver's VIRT_TO_BUS dependence in Kconfig.

Remove virt_to_bus(), just using the saved phy address to match.

Signed-off-by: Zhang Wei <wei.zhang@...escale.com>
---
 drivers/dma/fsldma.c |   13 +++++++++----
 1 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
index 71e1c32..899b0c0 100644
--- a/drivers/dma/fsldma.c
+++ b/drivers/dma/fsldma.c
@@ -495,15 +495,20 @@ static struct dma_async_tx_descriptor *fsl_dma_prep_memcpy(
  */
 static void fsl_dma_update_completed_cookie(struct fsl_dma_chan *fsl_chan)
 {
-	struct fsl_desc_sw *cur_desc;
+	struct fsl_desc_sw *cur_desc, *desc;
 	dma_addr_t ld_phy;
 
 	ld_phy = get_cdar(fsl_chan) & FSL_DMA_NLDA_MASK;
 
 	if (ld_phy) {
-		cur_desc = (struct fsl_desc_sw *)bus_to_virt(ld_phy);
-
-		if (cur_desc->async_tx.cookie) {
+		cur_desc = NULL;
+		list_for_each_entry(desc, &fsl_chan->ld_queue, node)
+			if (desc->async_tx.phys == ld_phy) {
+				cur_desc = desc;
+				break;
+			}
+
+		if (cur_desc && cur_desc->async_tx.cookie) {
 			if (dma_is_idle(fsl_chan))
 				fsl_chan->completed_cookie =
 					cur_desc->async_tx.cookie;
-- 
1.5.2

-
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/