On Tue, Sep 05, 2023 at 01:16:08PM -0700, Doug Anderson wrote: > > > --- > > > This commit is only compile-time tested. > > > > > > NOTE: this patch touches a lot more than other similar patches since > > > the bind() function is long and we want to make sure that we unset > > > the > > > drvdata if bind() fails. > > > > > > While making this patch, I noticed that the bind() function of this > > > driver is using "devm" and thus assumes it doesn't need to do much > > > explicit error handling. That's actually a bug. As per kernel docs > > > [1] > > > "the lifetime of the aggregate driver does not align with any of the > > > underlying struct device instances. Therefore devm cannot be used and > > > all resources acquired or allocated in this callback must be > > > explicitly released in the unbind callback". Fixing that is outside > > > the scope of this commit. > > > > > > [1] https://docs.kernel.org/driver-api/component.html > > > > > > > Noted, thanks. > > FWIW, I think that at least a few other DRM drivers handle this by > doing some of their resource allocation / acquiring in the probe() > function and then only doing things in the bind() that absolutely need > to be in the bind. ;-) That doesn't change much. The fundamental issue is that the DRM device sticks around until the last application that has an open fd to it closes it. So it doesn't have any relationship with the unbind/remove timing, and for all we know it can be there indefinitely, while the application continues to interact with the driver. Maxime
Attachment:
signature.asc
Description: PGP signature
