Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753453AbbKLI37 (ORCPT ); Thu, 12 Nov 2015 03:29:59 -0500 Received: from mail-io0-f194.google.com ([209.85.223.194]:33723 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751275AbbKLI36 (ORCPT ); Thu, 12 Nov 2015 03:29:58 -0500 MIME-Version: 1.0 In-Reply-To: <1447314579-31374-1-git-send-email-clabbe.montjoie@gmail.com> References: <1447314579-31374-1-git-send-email-clabbe.montjoie@gmail.com> Date: Thu, 12 Nov 2015 09:29:57 +0100 Message-ID: Subject: Re: [PATCH] mtd: nand: atmel_nand: fix a possible NULL dereference From: Joachim Eastwood To: LABBE Corentin Cc: Brian Norris , David Woodhouse , josh.wu@atmel.com, "linux-kernel@vger.kernel.org" , linux-mtd@lists.infradead.org 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: 1380 Lines: 36 On 12 November 2015 at 08:49, LABBE Corentin wrote: > of_match_device could return NULL, and so cause a NULL pointer > dereference later. > > Signed-off-by: LABBE Corentin > --- > drivers/mtd/nand/atmel_nand.c | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/drivers/mtd/nand/atmel_nand.c b/drivers/mtd/nand/atmel_nand.c > index 475c938..f3cf68b 100644 > --- a/drivers/mtd/nand/atmel_nand.c > +++ b/drivers/mtd/nand/atmel_nand.c > @@ -1495,9 +1495,12 @@ static int atmel_of_init_port(struct atmel_nand_host *host, > int ecc_mode; > struct atmel_nand_data *board = &host->board; > enum of_gpio_flags flags = 0; > + const struct of_device_id *of_id; > > - host->caps = (struct atmel_nand_caps *) > - of_match_device(atmel_nand_dt_ids, host->dev)->data; > + of_id = of_match_device(atmel_nand_dt_ids, host->dev); > + if (!of_id) > + return -ENODEV; > + host->caps = of_id->data; It might be cleaner to use of_device_get_match_data() here. regards, Joachim Eastwood -- 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/