From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Anders Roxell <anders.roxell@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, linux-mm <linux-mm@kvack.org>,
Arnd Bergmann <arnd@arndb.de>, Shuah Khan <shuah@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andrew Morton <akpm@linux-foundation.org>,
Pengfei Xu <pengfei.xu@intel.com>,
yi1.lai@intel.com
Subject: Re: selftests: gpio: crash on arm64
Date: Tue, 20 Jun 2023 19:40:21 +0300 [thread overview]
Message-ID: <ZJHWdcP+PDaNrw07@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdbUYWcFiRh+Y=MOekv2RjSP4sB2t5tVrSsz54Eez6wmVg@mail.gmail.com>
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@linaro.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
next prev parent reply other threads:[~2023-06-20 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 16:03 Naresh Kamboju
2023-03-09 17:50 ` Andy Shevchenko
2023-04-10 9:16 ` Naresh Kamboju
2023-04-11 8:57 ` Linus Walleij
2023-04-11 13:11 ` Bartosz Golaszewski
2023-06-20 16:40 ` Andy Shevchenko [this message]
2023-11-07 13:51 ` Naresh Kamboju
2023-11-15 1:42 ` andy.shevchenko
2023-11-15 15:37 ` Naresh Kamboju
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=ZJHWdcP+PDaNrw07@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=pengfei.xu@intel.com \
--cc=shuah@kernel.org \
--cc=yi1.lai@intel.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