Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755648Ab2JDJF7 (ORCPT ); Thu, 4 Oct 2012 05:05:59 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:37061 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751526Ab2JDJF5 (ORCPT ); Thu, 4 Oct 2012 05:05:57 -0400 MIME-Version: 1.0 In-Reply-To: <20121003092508.6a7da662@nehalam.linuxnetplumber.net> References: <1349281090-10013-20-git-send-email-peter.senna@gmail.com> <20121003092508.6a7da662@nehalam.linuxnetplumber.net> Date: Thu, 4 Oct 2012 11:05:55 +0200 Message-ID: Subject: Re: [PATCH 19/20] drivers/net/ethernet/marvell/skge.c: fix error return code From: Peter Senna Tschudin To: Stephen Hemminger Cc: mlindner@marvell.com, kernel-janitors@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1603 Lines: 60 > > Thanks for looking into these kind of problems. The contents > of the patch are correct, but the automated commit message is useless. > You shouldn't just blindly say what the automated > script was looking for, you should describe what the bug is so that evaluators > can decide what the impact is and if it should be backported to stable > and vendor kernels. > > Please resubmit the patchs with a reasonable analysis in the commit message. > Something like: > > There is a bug in skge driver. If alloc_etherdev() fails, then > skge_devinit() will return NULL, and the skge_probe function incorrectly > returns success 0. It should return -ENOMEM instead. > > Stephen, I do not want to include function names on the commit message. What do you think about this updated message, is it acceptable? --- --- --- This patch fixes a bug related to the return value of the function. In some error cases, the function return non-negative SUCCESS values, when the correct would be a negative ERROR value. A simplified version of the semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // ( if@p1 (\(ret < 0\|ret != 0\)) { ... return ret; } | ret@p1 = 0 ) ... when != ret = e1 when != &ret *if(...) { ... when != ret = e2 when forall return ret; } // --- --- --- Thanks, Peter -- Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/