On 09-03-2007 08:29, David Miller wrote: > From: Amit Choudhary <[EMAIL PROTECTED]> > Date: Thu, 8 Mar 2007 23:22:15 -0800 > >> Description: Check the return value of kmalloc() in function >> wrandom_set_nhinfo(), in file net/ipv4/multipath_wrandom.c. >> >> Signed-off-by: Amit Choudhary <[EMAIL PROTECTED]> > > This kind of patch has been submitted several times before and it's > never accepted because you have to do much more than this to recover > from the allocation error. > > There is no error status returned to the caller, so the callers assume > the operation succeeded, and will either OOPS or crash in some other > way. > > Therefore, just adding some NULL pointer checks and returning is not > going to fix this bug. > > The whole cahce-multipath subsystem has to have it's guts revamped for > proper error handling.
But until then it'll unnecessarily spoil linux opinion as regards stability and waste time of developers to check error messages. So, maybe it's less evil to check those NULLs where possible and add some WARN_ONs here and there... Regards, Jarek P. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
