On Wed, 15 Nov 2023 at 07:12, <andy.shevchenko@xxxxxxxxx> wrote: > > Tue, Nov 07, 2023 at 07:21:32PM +0530, Naresh Kamboju kirjoitti: > > On Tue, 20 Jun 2023 at 22:11, Andy Shevchenko > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > > On Tue, Apr 11, 2023 at 10:57:28AM +0200, Linus Walleij wrote: > > > > On Mon, Apr 10, 2023 at 11:16 AM Naresh Kamboju > > > > <naresh.kamboju@xxxxxxxxxx> wrote: > > ... > > > > > Add a pr_info() devm_gpio_chip_release() in drivers/gpio/gpiolib-devres.c > > > > and see if the callback is even called. I think this could be the > > > > problem: if that isn't cleaned up, there will be dangling references. > > > > > > Side note: Since we have devres tracepoints, your patch seems an overkill :-) > > > Just enable devres tracepoints and filter out by the function name. I believe > > > that should work. > > > > Since I have been tracking open issues on the stable-rc kernel, > > The reported problem on stable-rc linux.6.3.y has been solved > > on the stable-rc linux.6.6.y branch. > > > > Thanks for fixing this reported issue. > > > > Upstream links about this fix and discussion, > > I'm a bit lost. Is the [3] fixed? Is the fix the below mentioned commit? As per my understanding on this, The reported issue has been fixed with the below commit. > > > Commit daecca4b8433 > > gpiolib: Do not alter GPIO chip fwnode member > > > > [1] https://lore.kernel.org/linux-gpio/20230703142308.5772-4-andriy.shevchenko@xxxxxxxxxxxxxxx/ > > [2] https://lore.kernel.org/linux-gpio/CAMRc=MfFEBSeJ78NO7XeuzAMJ0KezEPAYWsWnFXXaRyQPAf3dA@xxxxxxxxxxxxxx/ > > [3] https://lore.kernel.org/linux-gpio/CA+G9fYv94gx8+-JMzbmQaue3q3y6QdBmsGUCdD-26X5XavL3Ag@xxxxxxxxxxxxxx/ > > -- > With Best Regards, > Andy Shevchenko - Naresh
