From: Jon Hunter <jonathanh@nvidia.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Rakesh Iyer <riyer@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: <linux-input@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] input: tegra-kbc: add NULL check on of_match_device() return value
Date: Fri, 7 Jul 2017 08:42:32 +0100 [thread overview]
Message-ID: <ec9b399b-ad14-21eb-9a2e-649f0dd1d489@nvidia.com> (raw)
In-Reply-To: <20170707062758.GA17584@embeddedgus>
On 07/07/17 07:27, Gustavo A. R. Silva wrote:
> Check return value from call to of_match_device()
> in order to prevent a NULL pointer dereference.
>
> In case of NULL print error message and return -ENODEV
>
> Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> ---
> drivers/input/keyboard/tegra-kbc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/input/keyboard/tegra-kbc.c b/drivers/input/keyboard/tegra-kbc.c
> index 0c07e10..742c5ac 100644
> --- a/drivers/input/keyboard/tegra-kbc.c
> +++ b/drivers/input/keyboard/tegra-kbc.c
> @@ -617,6 +617,10 @@ static int tegra_kbc_probe(struct platform_device *pdev)
> const struct of_device_id *match;
>
> match = of_match_device(tegra_kbc_of_match, &pdev->dev);
> + if (!match) {
> + dev_err(&pdev->dev, "failed to match device\n");
> + return -ENODEV;
> + }
Given that Tegra always uses device-tree, I believe that this cannot
happen and so this additional check is not needed.
Jon
--
nvpublic
next prev parent reply other threads:[~2017-07-07 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 6:27 Gustavo A. R. Silva
2017-07-07 7:42 ` Jon Hunter [this message]
2017-07-07 9:30 ` Thierry Reding
2017-07-10 17:42 ` Dmitry Torokhov
2017-07-10 19:24 ` Gustavo A. R. Silva
2017-07-10 19:27 ` Gustavo A. R. Silva
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=ec9b399b-ad14-21eb-9a2e-649f0dd1d489@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=dmitry.torokhov@gmail.com \
--cc=garsilva@embeddedor.com \
--cc=ldewangan@nvidia.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=riyer@nvidia.com \
--cc=thierry.reding@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome