From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: thierry.reding@gmail.com, wens@csie.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH v2 1/1] pwm: sun4i: fix a possible NULL dereference
Date: Wed, 24 Aug 2016 13:42:45 +0200 [thread overview]
Message-ID: <20160824114245.GA29212@Red> (raw)
In-Reply-To: <20160822065737.GA7104@lukather>
On Mon, Aug 22, 2016 at 08:57:37AM +0200, Maxime Ripard wrote:
> Hi,
>
> On Tue, Aug 16, 2016 at 03:18:06PM +0200, LABBE Corentin wrote:
> > of_match_device could return NULL, and so cause a NULL pointer
> > dereference later.
> >
> > For fixing this problem, we use of_device_get_match_data(), this will
> > simplify the code a little by using a standard function for
> > getting the match data.
> >
> > Reported-by: coverity (CID 1324139)
> > Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
> > ---
> > drivers/pwm/pwm-sun4i.c | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/drivers/pwm/pwm-sun4i.c b/drivers/pwm/pwm-sun4i.c
> > index 03a99a5..72f0060 100644
> > --- a/drivers/pwm/pwm-sun4i.c
> > +++ b/drivers/pwm/pwm-sun4i.c
> > @@ -309,9 +309,6 @@ static int sun4i_pwm_probe(struct platform_device *pdev)
> > struct resource *res;
> > u32 val;
> > int i, ret;
> > - const struct of_device_id *match;
> > -
> > - match = of_match_device(sun4i_pwm_dt_ids, &pdev->dev);
> >
> > pwm = devm_kzalloc(&pdev->dev, sizeof(*pwm), GFP_KERNEL);
> > if (!pwm)
> > @@ -326,7 +323,7 @@ static int sun4i_pwm_probe(struct platform_device *pdev)
> > if (IS_ERR(pwm->clk))
> > return PTR_ERR(pwm->clk);
> >
> > - pwm->data = match->data;
> > + pwm->data = of_device_get_match_data(&pdev->dev);
>
> How does that fix anything?
>
> If of_match_data fails, it will return NULL, and the NULL pointer
> dereference will occur in the exact same cases.
>
> You should just check for match to be NULL, and return in this case.
>
> Maxime
>
I apologize for havent seen this subsuquent NULL deref.
I send an updated version soon.
Regards
prev parent reply other threads:[~2016-08-24 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 13:18 [PATCH v2 0/1] pwm: sun4i: fix a possible NULL dereference LABBE Corentin
2016-08-16 13:18 ` [PATCH v2 1/1] " LABBE Corentin
2016-08-22 6:57 ` Maxime Ripard
2016-08-24 11:42 ` LABBE Corentin [this message]
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=20160824114245.GA29212@Red \
--to=clabbe.montjoie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=thierry.reding@gmail.com \
--cc=wens@csie.org \
/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;
as well as URLs for NNTP newsgroup(s).