From: Jonathan Cameron <jic23@kernel.org>
To: haibo.chen@nxp.com
Cc: lorenzo.bianconi83@gmail.com, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH] iio: imu: st_lsm6dsx: use dev_to_iio_dev() to get iio_dev struct
Date: Sat, 26 Feb 2022 18:19:37 +0000 [thread overview]
Message-ID: <20220226181937.4f2eeca6@jic23-huawei> (raw)
In-Reply-To: <1645702191-9400-1-git-send-email-haibo.chen@nxp.com>
On Thu, 24 Feb 2022 19:29:51 +0800
haibo.chen@nxp.com wrote:
> From: Haibo Chen <haibo.chen@nxp.com>
>
> After commit 8b7651f25962 ("iio: iio_device_alloc(): Remove
> unnecessary self drvdata"), current driver will meet kernel dump,
> kernel handle NULL pointer dereference.
Formal Fixes tag needed, but I can turn this into one whilst applying
and modify this description to talk about what no longer works rather
than the patch.
>
> Use dev_to_iio_dev() to get iio_dev struct.
>
> Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
Looks correct to me, so I'll queue it up in the iio/fixes-togreg branch.
Applied to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
> ---
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> index 93f0c6bce502..b1d8d5a66f01 100644
> --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> @@ -1633,7 +1633,7 @@ st_lsm6dsx_sysfs_sampling_frequency_avail(struct device *dev,
> struct device_attribute *attr,
> char *buf)
> {
> - struct st_lsm6dsx_sensor *sensor = iio_priv(dev_get_drvdata(dev));
> + struct st_lsm6dsx_sensor *sensor = iio_priv(dev_to_iio_dev(dev));
> const struct st_lsm6dsx_odr_table_entry *odr_table;
> int i, len = 0;
>
> @@ -1651,7 +1651,7 @@ static ssize_t st_lsm6dsx_sysfs_scale_avail(struct device *dev,
> struct device_attribute *attr,
> char *buf)
> {
> - struct st_lsm6dsx_sensor *sensor = iio_priv(dev_get_drvdata(dev));
> + struct st_lsm6dsx_sensor *sensor = iio_priv(dev_to_iio_dev(dev));
> const struct st_lsm6dsx_fs_table_entry *fs_table;
> struct st_lsm6dsx_hw *hw = sensor->hw;
> int i, len = 0;
prev parent reply other threads:[~2022-02-26 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 11:29 [PATCH] iio: imu: st_lsm6dsx: use dev_to_iio_dev() to get iio_dev struct haibo.chen
2022-02-26 18:19 ` 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=20220226181937.4f2eeca6@jic23-huawei \
--to=jic23@kernel.org \
--cc=haibo.chen@nxp.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=lorenzo.bianconi83@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