From: Martin Kepplinger <martink@posteo.de>
To: haibo.chen@nxp.com, jic23@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, pmeerw@pmeerw.net
Cc: Stable@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH] iio: mma8452: use the correct logic to get mma8452_data
Date: Tue, 22 Feb 2022 14:01:36 +0000 [thread overview]
Message-ID: <9bcd1b17f2d1b8829de94f37fbe1e84250f8716d.camel@posteo.de> (raw)
In-Reply-To: <1645497741-5402-1-git-send-email-haibo.chen@nxp.com>
Am Dienstag, dem 22.02.2022 um 10:42 +0800 schrieb haibo.chen@nxp.com:
> From: Haibo Chen <haibo.chen@nxp.com>
>
> The original logic to get mma8452_data is wrong, the *dev point to
> the device belong to iio_dev. we can't use this dev to find the
> correct i2c_client. The original logic happen to work because it
> finally use dev->driver_data to get iio_dev. Here use the API
> to_i2c_client() is wrong and make reader confuse. To correct the
> logic, it should be like this
>
> struct mma8452_data *data = iio_priv(dev_get_drvdata(dev));
>
> But after commit 8b7651f25962 ("iio: iio_device_alloc(): Remove
> unnecessary self drvdata"), the upper logic also can't work.
> When try to show the avialable scale in userspace, will meet kernel
> dump, kernel handle NULL pointer dereference.
>
> So use dev_to_iio_dev() to correct the logic.
>
> Fixes: c3cdd6e48e35 ("iio: mma8452: refactor for seperating chip
> specific data")
> Cc: <Stable@vger.kernel.org>
> Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
Reviewed-by: Martin Kepplinger <martink@posteo.de>
thank you for this fix!
> ---
> drivers/iio/accel/mma8452.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/accel/mma8452.c
> b/drivers/iio/accel/mma8452.c
> index 64b82b4503ad..0016bb947c10 100644
> --- a/drivers/iio/accel/mma8452.c
> +++ b/drivers/iio/accel/mma8452.c
> @@ -379,8 +379,8 @@ static ssize_t mma8452_show_scale_avail(struct
> device *dev,
> struct device_attribute
> *attr,
> char *buf)
> {
> - struct mma8452_data *data = iio_priv(i2c_get_clientdata(
> - to_i2c_client(dev)));
> + struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> + struct mma8452_data *data = iio_priv(indio_dev);
>
> return mma8452_show_int_plus_micros(buf, data->chip_info-
> >mma_scales,
> ARRAY_SIZE(data->chip_info->mma_scales));
next prev parent reply other threads:[~2022-02-22 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 2:42 [PATCH] iio: mma8452: use the correct logic to get mma8452_data haibo.chen
2022-02-22 14:01 ` Martin Kepplinger [this message]
2022-02-27 11:59 ` Jonathan Cameron
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=9bcd1b17f2d1b8829de94f37fbe1e84250f8716d.camel@posteo.de \
--to=martink@posteo.de \
--cc=Stable@vger.kernel.org \
--cc=haibo.chen@nxp.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=pmeerw@pmeerw.net \
/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