On Fri, 9 Apr 2010, Xiaotian Feng wrote: > > This doesn't work if the underlying slab allocator doesn't define > > __kmalloc_node_track_caller() regardless of whether CONFIG_TRACING is > > enabled or not. SLOB, for example, never defines it, and that's why the > > conditional exists in the way it currently does. > > > > Sorry, I didn't realized this, can we use (defined(CONFIG_TRACING) && > defined(CONFIG_SLAB)) ? > The valid configurations are (CONFIG_SLAB && (CONFIG_DEBUG_SLAB || CONFIG_TRACING)) || CONFIG_SLUB -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>