linux-kernel - Re: [REGRESSION] x86 vmalloc issue from recent 3.10.0+ commit

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: <20130710015936.GC13855@redhat.com>
Date:	Tue, 9 Jul 2013 21:59:36 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Michael L. Semon" <mlsemon35@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	d.hatayama@...fujitsu.com, akpm@...ux-foundation.org
Subject: Re: [REGRESSION] x86 vmalloc issue from recent 3.10.0+ commit

On Tue, Jul 09, 2013 at 09:51:32PM -0400, Michael L. Semon wrote:

 > kernel: [ 2580.395592] vmap allocation for size 20480 failed: use vmalloc=<size> to increase size.
 > kernel: [ 2580.395761] vmalloc: allocation failure: 16384 bytes

I was seeing a lot of these recently too.
(Though I also saw memory corruption afterwards possibly caused by
 a broken fallback path somewhere when that vmalloc fails)

http://comments.gmane.org/gmane.linux.kernel.mm/102895

	Dave

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