From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Zeng Heng <zengheng4@huawei.com>
Cc: <jic23@kernel.org>, <alexandru.ardelean@analog.com>,
<lars@metafoo.de>, <linux-iio@vger.kernel.org>,
<liwei391@huawei.com>
Subject: Re: [PATCH] iio: fix kobject_put warning in iio_device_register
Date: Fri, 11 Nov 2022 11:31:41 +0000 [thread overview]
Message-ID: <20221111113141.00000917@Huawei.com> (raw)
In-Reply-To: <20221110132615.331454-1-zengheng4@huawei.com>
On Thu, 10 Nov 2022 21:26:15 +0800
Zeng Heng <zengheng4@huawei.com> wrote:
> There is warning reported by kobject lib in kobject_put():
>
> kobject: '(null)' (00000000be81a546): is not initialized, yet kobject_put() is being called.
> WARNING: CPU: 0 PID: 535 at lib/kobject.c:718 kobject_put+0x12c/0x180
> Call Trace:
> cdev_device_add
> __iio_device_register
> __devm_iio_device_register
> tmp117_probe
>
> If don't need to register chardev for most of IIO devices,
> we just register them with device_add() only, and use device_del()
> to unregister them.
>
> Otherwise, when device_add() fails in internal and calls kobject_put()
> in error handling path, it would report warning because the device
> never be registered as chardev and there is no release function for it.
>
> Fixes: 8ebaa3ff1e71 ("iio: core: register chardev only if needed")
> Signed-off-by: Zeng Heng <zengheng4@huawei.com>
Interesting corner case. The cdev_device_add() call is fine with
!dev->devt which is what this code was taking advantage of. The exception
as you have highlighted is the error path of device_add().
So I think it should also cope with unwinding if device_add() fails
and not be calling cdev_del() Note that cdev_device_del() has the
appropriate guards to be safe whether or not (dev->devt) is true.
Perhaps change cdev_device_add() to have
rc = device_add(dev);
if (rc && dev->devt)
cdev_del(cdev);
return rc;
Jonathan
> ---
> drivers/iio/industrialio-core.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index 151ff3993354..f4f48bda07f7 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -1982,7 +1982,11 @@ int __iio_device_register(struct iio_dev *indio_dev, struct module *this_mod)
> /* assign device groups now; they should be all registered now */
> indio_dev->dev.groups = iio_dev_opaque->groups;
>
> - ret = cdev_device_add(&iio_dev_opaque->chrdev, &indio_dev->dev);
> + if (iio_dev_opaque->attached_buffers_cnt || iio_dev_opaque->event_interface)
> + ret = cdev_device_add(&iio_dev_opaque->chrdev, &indio_dev->dev);
> + else
> + ret = device_add(&indio_dev->dev);
> +
> if (ret < 0)
> goto error_unreg_eventset;
>
> @@ -2008,7 +2012,10 @@ void iio_device_unregister(struct iio_dev *indio_dev)
> {
> struct iio_dev_opaque *iio_dev_opaque = to_iio_dev_opaque(indio_dev);
>
> - cdev_device_del(&iio_dev_opaque->chrdev, &indio_dev->dev);
> + if (iio_dev_opaque->chrdev.kobj.state_initialized)
> + cdev_device_del(&iio_dev_opaque->chrdev, &indio_dev->dev);
> + else
> + device_del(&indio_dev->dev);
>
> mutex_lock(&iio_dev_opaque->info_exist_lock);
>
next prev parent reply other threads:[~2022-11-11 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 13:26 [PATCH] iio: fix kobject_put warning in iio_device_register Zeng Heng
2022-11-11 11:31 ` Jonathan Cameron [this message]
2022-11-11 12:05 ` Zeng Heng
2022-11-11 12:27 ` Zeng Heng
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=20221111113141.00000917@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alexandru.ardelean@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=zengheng4@huawei.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