linux-kernel - Re: [PATCH] bootmem: avoid DMA32 zone by default

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]

Date:	Thu, 21 Jan 2010 00:12:20 +0100
From:	Jiri Slaby <jslaby@...e.cz>
To:	Johannes Weiner <hannes@...xchg.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Ralf Baechle <ralf@...ux-mips.org>,
	x86@...nel.org, stable@...nel.org
Subject: Re: [PATCH] bootmem: avoid DMA32 zone by default

On 01/20/2010 11:53 PM, Johannes Weiner wrote:
> I cc'd stable because this affects already released kernels.  But since this is
> the first report of DMA32 memory exhaustion through bootmem that I hear of,

Just for how the setup look like:
128G of RAM, flat mapping
sizeof(struct page)=56
0-1.75G mem_map
1.75-2G vfs caches, console and others. initrd reservation
2-4G reserved by BIOS

Kernel panics with out of memory when swiotlb tries to allocate 64M of
"low" bootmem.

-- 
js
suse labs
--
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/