linux-kernel - Re: [patch] bootmem: use MAX_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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060728131306.GA32513@elte.hu>
Date:	Fri, 28 Jul 2006 15:13:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Andrew Morton <akpm@...l.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT


* Heiko Carstens <heiko.carstens@...ibm.com> wrote:

> From: Heiko Carstens <heiko.carstens@...ibm.com>
> 
> __alloc_bootmem_low() and __alloc_bootmem_low_node() should use 
> MAX_DMA_ADDRESS as limit which is per architecture instead of a global 
> LOW32LIMIT. Otherwise the bootmem allocator may return addresses to 
> memory regions which cannot be used for DMA access.

> -#define LOW32LIMIT 0xffffffff

>  		if ((ptr = __alloc_bootmem_core(bdata, size,
> -						 align, goal, LOW32LIMIT)))
> +						 align, goal, MAX_DMA_ADDRESS)))

but this limits things to 16MB on i686. Are you sure this wont break 
anything?

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