Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Christoph Lameter
Date: Wednesday, February 27, 2008 - 3:15 pm

On Tue, 19 Feb 2008, Pekka Enberg wrote:


Yeah that would determine if its the fastpath code. Note that the new 
fastpath code may expose bugs that so far have been tolerated by the slab 
allocators. If a store of a NULL to the first word of an object occurs 
then this will be tolerated in 2.6.24 because slub will take it as the end 
of the object list and just forget about the remaining objects. The 
fastpath code will terminate with a NULL pointer deref.

Enabling full debugging may get rid of the race due to the slowdown. It 
could help to just enable minimal debugging for the slab cache in which we 
see the issue.

So do

slub_debug=F,<affected cache>

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Zhang, Yanmin, (Thu Feb 14, 11:47 pm)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Christoph Lameter, (Fri Feb 15, 9:42 am)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Andrew Morton, (Mon Feb 18, 5:59 am)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Arjan van de Ven, (Mon Feb 18, 9:52 am)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Zhang, Yanmin, (Mon Feb 18, 8:14 pm)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Zhang, Yanmin, (Tue Feb 19, 12:03 am)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Pekka Enberg, (Tue Feb 19, 12:38 am)
Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1, Christoph Lameter, (Wed Feb 27, 3:15 pm)