On Thu, 2 Aug 2012, Christoph Lameter wrote: > Instead of using s == NULL use an errorcode. This allows much more > detailed diagnostics as to what went wrong. As we add more functionality > from the slab allocators to the common kmem_cache_create() function we will > also add more error conditions. > > Print the error code during the panic as well as in a warning if the module > can handle failure. The API for kmem_cache_create() currently does not allow > the returning of an error code. Return NULL but log the cause of the problem > in the syslog. > I like how this also dumps the stack for any kmem_cache_create() that fails. > Signed-off-by: Christoph Lameter <cl@xxxxxxxxx> > Acked-by: David Rientjes <rientjes@xxxxxxxxxx> -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>