On Thu, Nov 07, 2013 at 09:27:32AM +0100, Andreas Herrmann wrote: > On Wed, Nov 06, 2013 at 04:38:10PM -0500, Christoph Lameter wrote: > > On Wed, 6 Nov 2013, Andreas Herrmann wrote: > > > > > Would be nice, if your patch is pushed upstream asap. > > > > Ok so this is a > > > > Tested-by: Andreas Herrmann <andreas.herrm...@calxeda.com> > > > > I think? > > Yes.
And for sake of completeness. Here is some debug output with a kernel that had your "slub: Handle NULL parameter in kmem_cache_flags" patch applied. And of course there were a couple of unnamed slabs: ... .bss : 0xc089fd80 - 0xc094cc4c ( 692 kB) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name (c06fc90c): kmem_cache_node slub_debug_slabs (c2956a08): skbuff_fclone_cache, name (c06fc91c): kmem_cache → slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) slub_debug_slabs (c2956a08): skbuff_fclone_cache, name ( (null)): (null) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 ... The third one is wheree the panic happened w/o the fix. Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/