[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJHWdcP+PDaNrw07@smile.fi.intel.com>
Date: Tue, 20 Jun 2023 19:40:21 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Anders Roxell <anders.roxell@...aro.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>, linux-mm <linux-mm@...ck.org>,
Arnd Bergmann <arnd@...db.de>, Shuah Khan <shuah@...nel.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Andrew Morton <akpm@...ux-foundation.org>,
Pengfei Xu <pengfei.xu@...el.com>, yi1.lai@...el.com
Subject: Re: selftests: gpio: crash on arm64
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@...aro.org> 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.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists