From: Jonathan Cameron <jic23@kernel.org>
To: "Patrik Dahlström" <risca@dalakolonin.se>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, hns@goldelico.com
Subject: Re: [PATCH] iio: adc: palmas_gpadc: fix NULL dereference on rmmod
Date: Sat, 18 Mar 2023 16:30:33 +0000 [thread overview]
Message-ID: <20230318163033.161d6fd5@jic23-huawei> (raw)
In-Reply-To: <20230313205029.1881745-1-risca@dalakolonin.se>
On Mon, 13 Mar 2023 21:50:29 +0100
Patrik Dahlström <risca@dalakolonin.se> wrote:
> Calling dev_to_iio_dev() on a platform device pointer is undefined and
> will make adc NULL.
>
> Signed-off-by: Patrik Dahlström <risca@dalakolonin.se>
Hi Patrik,
Looks good so applied to the fixes-togreg branch of iio.git.
Whilst we are here, this would be a trivial driver to take fully device
managed. The only slightly messy bit is that it would need
a devm_add_action_or_reset() + custom callback to handle the
device_wakeup_enable().
On the off chance you can test it I'll send a patch in a few mins.
Note that will depend on this one going up stream first and that
I haven't done more than build test it.
Thanks,
Jonathan
> ---
> drivers/iio/adc/palmas_gpadc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/palmas_gpadc.c b/drivers/iio/adc/palmas_gpadc.c
> index 61e80bf3d05e..6db6f3bc768a 100644
> --- a/drivers/iio/adc/palmas_gpadc.c
> +++ b/drivers/iio/adc/palmas_gpadc.c
> @@ -638,7 +638,7 @@ static int palmas_gpadc_probe(struct platform_device *pdev)
>
> static int palmas_gpadc_remove(struct platform_device *pdev)
> {
> - struct iio_dev *indio_dev = dev_to_iio_dev(&pdev->dev);
> + struct iio_dev *indio_dev = dev_get_drvdata(&pdev->dev);
> struct palmas_gpadc *adc = iio_priv(indio_dev);
>
> if (adc->wakeup1_enable || adc->wakeup2_enable)
next prev parent reply other threads:[~2023-03-18 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:50 [PATCH] iio: adc: palmas_gpadc: fix NULL dereference on rmmod Patrik Dahlström
2023-03-18 16:30 ` Jonathan Cameron [this message]
2023-03-18 19:22 ` Patrik Dahlström
2023-03-19 15:32 ` Jonathan Cameron
2023-03-19 15:45 ` H. Nikolaus Schaller
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=20230318163033.161d6fd5@jic23-huawei \
--to=jic23@kernel.org \
--cc=hns@goldelico.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=risca@dalakolonin.se \
/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