On 3/23/23 18:36, Maxime Ripard wrote:
On Thu, Mar 23, 2023 at 03:02:03PM +0200, Matti Vaittinen wrote:
On 3/23/23 14:29, Maxime Ripard wrote:
On Thu, Mar 23, 2023 at 02:16:52PM +0200, Matti Vaittinen wrote:
This is the description of what was happening:
Thanks Maxime. Do I read this correcty. The devm_ unwinding not being done
when root_device_register() is used is not because root_device_unregister()
would not trigger the unwinding - but rather because DRM code on top of this
device keeps the refcount increased?
There's a difference of behaviour between a root_device and any device
with a bus: the root_device will only release the devm resources when
it's freed (in device_release), but a bus device will also do it in
device_del (through bus_remove_device() -> device_release_driver() ->
device_release_driver_internal() -> __device_release_driver() ->
device_unbind_cleanup(), which are skipped (in multiple places) if
there's no bus and no driver attached to the device).
It does affect DRM, but I'm pretty sure it will affect any framework
that deals with device hotplugging by deferring the framework structure
until the last (userspace) user closes its file descriptor. So I'd
assume that v4l2 and cec at least are also affected, and most likely
Thanks for the explanation and patience :)
If this is the case, then it sounds like a DRM specific issue to me.
I mean, I guess. One could also argue that it's because IIO doesn't
properly deal with hotplugging.
I must say I haven't been testing the IIO registration API. I've only
tested the helper API which is not backed up by any "IIO device". (This
is fine for the helper because it must by design be cleaned-up only
after the IIO-deregistration).
After your explanation here, I am not convinced IIO wouldn't see the
same issue if I was testing the devm_iio_device_alloc() & co.
I'm not sure how that helps. Those are
common helpers which should accommodate every framework,
Ok. Fair enough. Besides, if the root-device was sufficient - then I
would actually not see the need for a helper. People could in that case
directly use the root_device_register(). So, if helpers are provided
they should be backed up by a device with a bus then.
and your second
patch breaks the kunit tests for DRM anyway.
Oh, I must have made an error there. It was supposed to be just a
refactoring with no functional changes. Sorry about that. Anyways, that
patch can be forgotten as Greg opposes using the platform devices in
Thanks for the patience and the explanation. Now I understand a generic
test device needs to sit on a bus.
Whether it is a feature or bug is beyond my knowledge. Still, I would
not say using the root_device_[un]register() in generic code is not
feasible - unless all other subsytems have similar refcount handling.
Sure thing using root_device_register() root_device_unregister() in DRM does
not work as such. This, however, does not mean the generic kunit helpers
should use platform_devices to force unwinding?
platform_devices were a quick way to get a device that would have a bus
and a driver bound to fall into the right patch above. We probably
shouldn't use platform_devices and a kunit_device sounds like the best
idea, but the test linked in the original mail I pointed you to should
work with whatever we come up with. It works with multiple (platform,
PCI, USB, etc) buses, so the mock we create should behave like their
real world equivalents.
As I said, in my very specific IIO related test the test device does not
need a bus. Hence I'll drop the 'generic helpers' from this series.
Linux kernel developer at ROHM Semiconductors
~~ When things go utterly wrong vim users can always type :help! ~~