Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753403AbbKLIg6 (ORCPT ); Thu, 12 Nov 2015 03:36:58 -0500 Received: from mail-wm0-f46.google.com ([74.125.82.46]:34760 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751275AbbKLIg4 convert rfc822-to-8bit (ORCPT ); Thu, 12 Nov 2015 03:36:56 -0500 MIME-Version: 1.0 In-Reply-To: <20151112082617.GE24008@pengutronix.de> References: <1447314423-31225-1-git-send-email-clabbe.montjoie@gmail.com> <20151112082617.GE24008@pengutronix.de> Date: Thu, 12 Nov 2015 09:36:55 +0100 Message-ID: Subject: Re: [PATCH] mtd: nand: mxc_nand: fix a possible NULL dereference From: Frans Klaver To: =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= Cc: LABBE Corentin , baruch@tkos.co.il, Brian Norris , David Woodhouse , =?UTF-8?Q?Krzysztof_Koz=C5=82owski?= , Luis de Bethencourt , s.hauer@pengutronix.de, "linux-kernel@vger.kernel.org" , linux-mtd@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1473 Lines: 40 On Thu, Nov 12, 2015 at 9:26 AM, Uwe Kleine-König wrote: > On Thu, Nov 12, 2015 at 09:03:11AM +0100, Frans Klaver wrote: >> Hi, >> >> On Thu, Nov 12, 2015 at 8:46 AM, LABBE Corentin >> wrote: >> > of_match_device could return NULL, and so cause a NULL pointer >> > dereference later. >> >> Did you actually run into this? It seems to me that this driver is >> only probed if and only if we have a match and that therefore >> of_match_device will always return a valid pointer (it is using the >> same match table). Am I missing something? > > Yes, you're missing something. The driver would probe for a dt snippet > like: > > mxc_nand { > compatible = "foobar"; > } > > In this case dev->of_node is non-NULL but of_match_device(mxcnd_dt_ids, > dev) is. > > (I didn't actually test this, so there is a chance I'm wrong here. And > if not I wonder if it is sensible at all to match the device name on > driver name for of-created platform devices.) Yea, looks like you're right. platform devices check a number of things to determine a match, among which is driver name if all else fails (platform.c, platform_match()). Thanks, Frans -- 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/