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: Wed, 24 Mar 2010 20:22:08 +0100 From: Eric Dumazet <eric.dumazet@...il.com> To: Christoph Lameter <cl@...ux-foundation.org> Cc: Pekka J Enberg <penberg@...helsinki.fi>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] slub: Potential stack overflow Le mercredi 24 mars 2010 à 14:16 -0500, Christoph Lameter a écrit : > On Wed, 24 Mar 2010, Eric Dumazet wrote: > > > I discovered that we can overflow stack if CONFIG_SLUB_DEBUG=y and use > > slabs with many objects, since list_slab_objects() and process_slab() > > use DECLARE_BITMAP(map, page->objects); > > Maybe we better allocate the bitmap via kmalloc then. > Hmm... Are we allowed to nest in these two functions ? GFP_KERNEL, GFP_ATOMIC ? These are debugging functions, what happens if kmalloc() returns NULL ? -- 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