| 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
| ||
|
Date: Mon, 3 Sep 2012 13:00:04 +0200 From: Jan Luebbe <jlu@...gutronix.de> To: Joerg Roedel <joerg.roedel@....com> Cc: linux-kernel@...r.kernel.org, Jan Luebbe <jlu@...gutronix.de> Subject: [PATCH] lib/dma-debug: check for vmalloc buffers used with the DMA-API Signed-off-by: Jan Luebbe <jlu@...gutronix.de> --- I'm not sure why we don't check for high memory, is there any problem with this approach? lib/dma-debug.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lib/dma-debug.c b/lib/dma-debug.c index 66ce414..7d60ff0 100644 --- a/lib/dma-debug.c +++ b/lib/dma-debug.c @@ -944,6 +944,9 @@ static void check_for_illegal_area(struct device *dev, void *addr, unsigned long if (overlap(addr, len, _text, _etext) || overlap(addr, len, __start_rodata, __end_rodata)) err_printk(dev, NULL, "DMA-API: device driver maps memory from kernel text or rodata [addr=%p] [len=%lu]\n", addr, len); + if (is_vmalloc_or_module_addr(addr) || + is_vmalloc_or_module_addr(addr+len)) + err_printk(dev, NULL, "DMA-API: device driver maps memory from vmalloc or module address range [addr=%p] [len=%lu]\n", addr, len); } static void check_sync(struct device *dev, -- 1.7.10.4 -- 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/
Powered by blists - more mailing lists