From: Jonathan Cameron <jic23@kernel.org>
To: Tomasz Duszynski <tduszyns@gmail.com>
Cc: Kangjie Lu <kjlu@umn.edu>,
pakki001@umn.edu, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Stefan Agner <stefan@agner.ch>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: max9611: fix a NULL pointer dereference
Date: Sat, 9 Mar 2019 18:34:37 +0000 [thread overview]
Message-ID: <20190309183437.479f90a1@archlinux> (raw)
In-Reply-To: <20190309151916.GB7820@arch>
On Sat, 9 Mar 2019 16:19:17 +0100
Tomasz Duszynski <tduszyns@gmail.com> wrote:
> On Fri, Mar 08, 2019 at 10:51:40PM -0600, Kangjie Lu wrote:
> > of_match_device may return NULL when it fails, and in this case,
> > there will be a NULL pointer dereference. The fix returns
> > EINVAL when of_match_device returns NULL.
> >
> > Signed-off-by: Kangjie Lu <kjlu@umn.edu>
> > ---
> > drivers/iio/adc/max9611.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/iio/adc/max9611.c b/drivers/iio/adc/max9611.c
> > index 917223d5ff5b..531b6614ea29 100644
> > --- a/drivers/iio/adc/max9611.c
> > +++ b/drivers/iio/adc/max9611.c
> > @@ -524,13 +524,16 @@ static int max9611_probe(struct i2c_client *client,
> > {
> > const char * const shunt_res_prop = "shunt-resistor-micro-ohms";
> > const struct device_node *of_node = client->dev.of_node;
> > - const struct of_device_id *of_id =
> > - of_match_device(max9611_of_table, &client->dev);
>
> Given we got to this point how this can go wrong?
If this is to squash a warning then there may be some argument
even though it can't actually fail. If there is such a warning
please put it in the patch description.
Thanks,
Jonathan
>
> > + const struct of_device_id *of_id;
> > struct max9611_dev *max9611;
> > struct iio_dev *indio_dev;
> > unsigned int of_shunt;
> > int ret;
> >
> > + of_id = of_match_device(max9611_of_table, &client->dev);
> > + if (!of_id)
> > + return -EINVAL;
> > +
> > indio_dev = devm_iio_device_alloc(&client->dev, sizeof(*max9611));
> > if (!indio_dev)
> > return -ENOMEM;
> > --
> > 2.17.1
> >
prev parent reply other threads:[~2019-03-09 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 4:51 [PATCH] iio: max9611: fix a NULL pointer dereference Kangjie Lu
2019-03-09 15:19 ` Tomasz Duszynski
2019-03-09 18:34 ` Jonathan Cameron [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=20190309183437.479f90a1@archlinux \
--to=jic23@kernel.org \
--cc=kjlu@umn.edu \
--cc=knaack.h@gmx.de \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=pmeerw@pmeerw.net \
--cc=stefan@agner.ch \
--cc=tduszyns@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