linux-kernel - [PATCH] Fix DMA access of block device in 64-bit kernel on some non-x86 systems with 4GB or upper 4GB memory

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

Message-ID: <47CD179B.3000806@windriver.com>
Date:	Tue, 04 Mar 2008 17:34:19 +0800
From:	yshi <yang.shi@...driver.com>
To:	axboe@...nel.dk
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: [PATCH] Fix DMA access of block device in 64-bit kernel on some non-x86
 systems with 4GB or upper 4GB memory

For some non-x86 systems with 4GB or upper 4GB memory,
we need increase the range of addresses that can be
used for direct DMA in 64-bit kernel.

Signed-off-by: Yang Shi <yang.shi@...driver.com>
---
b/block/blk-settings.c |    2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---

--- a/block/blk-settings.c      2008-03-03 17:11:25.000000000 +0800
+++ b/block/blk-settings.c      2008-03-03 17:11:42.000000000 +0800
@@ -140,7 +140,7 @@ void blk_queue_bounce_limit(struct reque
       /* Assume anything <= 4GB can be handled by IOMMU.
          Actually some IOMMUs can handle everything, but I don't
          know of a way to test this here. */
-       if (b_pfn < (min_t(u64, 0xffffffff, BLK_BOUNCE_HIGH) >> 
PAGE_SHIFT))
+       if (b_pfn <= (min_t(u64, 0xffffffff, BLK_BOUNCE_HIGH) >> 
PAGE_SHIFT))
               dma = 1;
       q->bounce_pfn = max_low_pfn;
#else
--
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/