3.17-stable review patch. If anyone has any objections, please let me know.
------------------ From: Laurent Pinchart <[email protected]> commit f022d8cb7ec70fe8edd56383d876001317ee76b1 upstream. If activation of the CMA area fails its mutex won't be initialized, leading to an oops at allocation time when trying to lock the mutex. Fix this by setting the cma area count field to 0 when activation fails, leading to allocation returning NULL immediately. Signed-off-by: Laurent Pinchart <[email protected]> Acked-by: Michal Nazarewicz <[email protected]> Signed-off-by: Marek Szyprowski <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> --- mm/cma.c | 1 + 1 file changed, 1 insertion(+) --- a/mm/cma.c +++ b/mm/cma.c @@ -123,6 +123,7 @@ static int __init cma_activate_area(stru err: kfree(cma->bitmap); + cma->count = 0; return -EINVAL; } -- 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/
