From: Lars-Peter Clausen <lars@metafoo.de>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: inkern: add error case in iio_channel_get()
Date: Mon, 10 Sep 2012 11:24:08 +0200 [thread overview]
Message-ID: <504DB1B8.4020608@metafoo.de> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F41EF45EB@DQHE02.ent.ti.com>
On 09/10/2012 10:02 AM, Kim, Milo wrote:
> The datasheet name is defined in the IIO driver.
> On the other hand, the adc_channel_label is configured in
> the platform machine side.
> If the datasheet name is not matched with any adc_channel_label,
> the iio_channel_get() should be returned as error for preventing
> using invalid IIO channel data.
>
> Moreover, this patch detects NULL pointer dereference problem at early time.
> In general, the IIO driver just accesses to any member of the iio_chan_spec
> in own xxx_read_raw() function.
> If the iio_chan_spec is invalid pointer, NULL dereference problem may occur
> such like 'iio_chan_spec->channel' or 'iio_chan_spec->type'.
> If the iio_channel_get() gets failed in the IIO consumer,
> then no read_raw() operation proceeds.
>
> Signed-off-by: Milo(Woogyom) Kim <milo.kim@ti.com>
> ---
> drivers/iio/inkern.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/inkern.c b/drivers/iio/inkern.c
> index 1faa240..a5caf6b 100644
> --- a/drivers/iio/inkern.c
> +++ b/drivers/iio/inkern.c
> @@ -136,11 +136,15 @@ struct iio_channel *iio_channel_get(const char *name, const char *channel_name)
>
> channel->indio_dev = c->indio_dev;
>
> - if (c->map->adc_channel_label)
> + if (c->map->adc_channel_label) {
> channel->channel =
> iio_chan_spec_from_name(channel->indio_dev,
> c->map->adc_channel_label);
>
> + if (channel->channel == NULL)
> + return ERR_PTR(-ENODEV);
This introduces a memory leak. You need to free channel before returning.
> + }
> +
> return channel;
> }
> EXPORT_SYMBOL_GPL(iio_channel_get);
prev parent reply other threads:[~2012-09-10 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 8:02 [PATCH 2/2] iio: inkern: add error case in iio_channel_get() Kim, Milo
2012-09-10 8:02 ` Kim, Milo
2012-09-10 9:16 ` Jonathan Cameron
2012-09-14 0:59 ` Kim, Milo
2012-09-14 8:24 ` Jonathan Cameron
2012-09-17 8:46 ` Kim, Milo
2012-09-17 8:46 ` Kim, Milo
2012-09-10 9:24 ` Lars-Peter Clausen [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=504DB1B8.4020608@metafoo.de \
--to=lars@metafoo.de \
--cc=Milo.Kim@ti.com \
--cc=jic23@cam.ac.uk \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.