Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752066AbbKIAVq (ORCPT ); Sun, 8 Nov 2015 19:21:46 -0500 Received: from mail-ig0-f179.google.com ([209.85.213.179]:35340 "EHLO mail-ig0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751417AbbKIAVn (ORCPT ); Sun, 8 Nov 2015 19:21:43 -0500 MIME-Version: 1.0 In-Reply-To: <1446738939-22320-1-git-send-email-clabbe.montjoie@gmail.com> References: <1446738939-22320-1-git-send-email-clabbe.montjoie@gmail.com> From: Alexandre Courbot Date: Mon, 9 Nov 2015 09:21:23 +0900 Message-ID: Subject: Re: [PATCH] gpio: 74xx: fix a possible NULL dereference To: LABBE Corentin Cc: Linus Walleij , "linux-gpio@vger.kernel.org" , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 38 On Fri, Nov 6, 2015 at 12:55 AM, LABBE Corentin wrote: > of_match_device could return NULL, and so cause a NULL pointer > dereference later at line 132: > priv->flags = (uintptr_t) of_id->data; > > Reported-by: coverity (CID 1324141) > Signed-off-by: LABBE Corentin > --- > drivers/gpio/gpio-74xx-mmio.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/gpio/gpio-74xx-mmio.c b/drivers/gpio/gpio-74xx-mmio.c > index 6ed7c0f..4a7be0f 100644 > --- a/drivers/gpio/gpio-74xx-mmio.c > +++ b/drivers/gpio/gpio-74xx-mmio.c > @@ -120,6 +120,9 @@ static int mmio_74xx_gpio_probe(struct platform_device *pdev) > void __iomem *dat; > int err; > > + if (!of_id) > + return -ENODEV; > + Nit: in that case, could you also move the assignment of of_id to its own line right above these added lines? It would keep things in the same place and the current layout does not even save any space since the declaration of of_id currently takes two lines because the assignment makes it longer than 80 chars... With this, Reviewed-by: Alexandre Courbot -- 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/