Re: [linux-next][PATCH] mm: slub: work around unneeded lockdep warning

On Fri, 24 Jan 2014, Dave Hansen wrote: > From: Dave Hansen > > The slub code does some setup during early boot in > early_kmem_cache_node_alloc() with some local data. There is no > possible way that another CPU can see this data, so the slub code > doesn't unnecessarily lock it. However,

Re: [linux-next][PATCH] mm: slub: work around unneeded lockdep warning

On Fri, 24 Jan 2014, Dave Hansen wrote: From: Dave Hansen dave.han...@linux.intel.com The slub code does some setup during early boot in early_kmem_cache_node_alloc() with some local data. There is no possible way that another CPU can see this data, so the slub code doesn't unnecessarily

[linux-next][PATCH] mm: slub: work around unneeded lockdep warning

I think this is a next-only thing. Pekka, can you pick this up, please? -- From: Dave Hansen The slub code does some setup during early boot in early_kmem_cache_node_alloc() with some local data. There is no possible way that another CPU can see this data, so the slub code doesn't

[linux-next][PATCH] mm: slub: work around unneeded lockdep warning

I think this is a next-only thing. Pekka, can you pick this up, please? -- From: Dave Hansen dave.han...@linux.intel.com The slub code does some setup during early boot in early_kmem_cache_node_alloc() with some local data. There is no possible way that another CPU can see this data, so the