Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751921AbbKJSUv (ORCPT ); Tue, 10 Nov 2015 13:20:51 -0500 Received: from mail-pa0-f42.google.com ([209.85.220.42]:34951 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbbKJSUu (ORCPT ); Tue, 10 Nov 2015 13:20:50 -0500 Date: Tue, 10 Nov 2015 10:20:47 -0800 From: Brian Norris To: Saurabh Sengar Cc: andy.shevchenko@gmail.com, joern@lazybastard.org, dwmw2@infradead.org, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] mtd: phram: error handling Message-ID: <20151110182047.GP12143@google.com> References: <1447050198-20562-1-git-send-email-saurabh.truth@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1447050198-20562-1-git-send-email-saurabh.truth@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2020 Lines: 57 On Mon, Nov 09, 2015 at 11:53:18AM +0530, Saurabh Sengar wrote: > registering the device with NULL pointer can lead to crash, > hence fixing it > > Signed-off-by: Saurabh Sengar > --- > > Andy Shevchenko wrote: > > Hmm… Why not just checking it before an register attempt? I think user > > is in right to know as many problems as they have at one shot, with > > your patch if there are two problems the user has to try twice. > Yes, taken your feedback, fixing it here in v2 as you recommended > > drivers/mtd/devices/phram.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/mtd/devices/phram.c b/drivers/mtd/devices/phram.c > index 8b66e52..46b7a8a 100644 > --- a/drivers/mtd/devices/phram.c > +++ b/drivers/mtd/devices/phram.c > @@ -257,6 +257,9 @@ static int phram_setup(const char *val) > parse_err("illegal device length\n"); > } > > + if(!name) > + return -EINVAL; I'm not sure how this is supposed to do anything... just because you kfree()'d the name doesn't mean it is NULL. In fact, I don't see how you'd get name==NULL at all. It is assigned once (in parse_name()), and if it's NULL, we already exit early. And 'name' is never modified after that point. So... did you test your patch? (*looks at the existing code a bit more*) Hey, I think your patch is all futile anyway. Did you notice that there's a "return" statement embedded in the parse_err() macro? So there was no bug in the first place, and I think you're just blowing smoke. Please verify that you're actually fixing bugs, and please test your patches. Otherwise, you're wasting my time. Brian > + > ret = register_device(name, start, len); > if (!ret) > pr_info("%s device: %#llx at %#llx\n", name, len, start); > -- > 1.9.1 > -- 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/