All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: LABBE Corentin <montjoie.mailing@gmail.com>,
	LABBE Corentin <clabbe.montjoie@gmail.com>,
	gnurou@gmail.com, ldewangan@nvidia.com, swarren@wwwdotorg.org,
	wsa@the-dreams.de, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] i2c: tegra: fix a possible NULL dereference
Date: Thu, 12 Nov 2015 14:45:20 +0100	[thread overview]
Message-ID: <20151112134519.GJ24008@pengutronix.de> (raw)
In-Reply-To: <20151112132837.GF31671@ulmo>

On Thu, Nov 12, 2015 at 02:28:37PM +0100, Thierry Reding wrote:
> On Thu, Nov 12, 2015 at 01:54:22PM +0100, LABBE Corentin wrote:
> > On Thu, Nov 12, 2015 at 01:29:23PM +0100, Thierry Reding wrote:
> > > On Thu, Nov 12, 2015 at 08:26:03AM +0100, LABBE Corentin wrote:
> > > > of_match_device could return NULL, and so cause a NULL pointer
> > > 
> > > No. There is no way that of_match_device() can ever fail. The driver
> > > core uses the same table to match the OF device to the driver, so the
> > > only case where of_match_device() would return NULL is if no match was
> > > found, in which case the tegra_i2c_probe() function would never have
> > > been called in the first place.
> > > 
> > > Thierry
> > > 
> > 
> > In a parallel thread for i2c-rcar, the conclusion was different.
> > https://lkml.org/lkml/2015/11/12/83
> 
> The conclusion was the same: there should be no case where this happens.
> The example that Uwe gave is hypothetical and not valid DT in the first
> place. So instead of chickening out I think it'd be better to just crash
> to make sure people fix the DT.

It depends in your trust in the DT. Just because it's not advisable to
do something that is not documented usually isn't a good excuse to not
handle broken input. That't the case for webserver requests, arguments
to system calls and several more. I admit DT is a bit special because
you have to assume it's trusted, but still handling errors in a sane way
is IMHO nice.

> On a side-note I think that platform_match() should be stricter and do
> something like this instead:
> 
> 	if (dev->of_node) {
> 		if (of_driver_match_device(dev, drv))
> 			return 1;
> 
> 		return 0;
> 	}
That's equivalent to

	if (dev->of_node)
		return of_driver_match_device(dev, drv);

and was already suggested in the thread referenced from my reply to
http://article.gmane.org/gmane.linux.kernel/2083641 :-)

Best regards
Uwe 

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-11-12 13:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  7:26 [PATCH] i2c: tegra: fix a possible NULL dereference LABBE Corentin
2015-11-12 12:29 ` Thierry Reding
2015-11-12 12:54   ` LABBE Corentin
2015-11-12 13:28     ` Thierry Reding
2015-11-12 13:28       ` Thierry Reding
2015-11-12 13:45       ` Uwe Kleine-König [this message]
     [not found]         ` <20151112134519.GJ24008-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-11-12 13:55           ` Thierry Reding
2015-11-12 13:55             ` Thierry Reding
2015-11-12 14:54             ` LABBE Corentin
2015-11-12 16:14               ` Thierry Reding
2015-11-12 16:14                 ` Thierry Reding
2016-01-23 11:07               ` Wolfram Sang
2016-01-23 11:07                 ` Wolfram Sang
2016-01-23 10:56           ` Wolfram Sang
2016-01-23 10:56             ` Wolfram Sang
2015-11-12 13:40   ` Jon Hunter
2015-11-12 13:40     ` Jon Hunter
2015-11-12 13:55     ` Thierry Reding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151112134519.GJ24008@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=clabbe.montjoie@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=montjoie.mailing@gmail.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.