diff options
| author | Myeonghun Pak <mhun512@gmail.com> | 2026-09-13 00:03:12 -0400 |
|---|---|---|
| committer | Linus Walleij <linusw@kernel.org> | 2026-09-16 19:19:04 +0200 |
| commit | 1d9bb9c870632adea249cfdec49ac37e6f069164 (patch) | |
| tree | 0f43b17d15c13eb839957d90f7c9d79052023617 /tools/perf/scripts/python/stackcollapse.py | |
| parent | ef56085dfd1df3a53ecce8a4ff440cf6d67f430d (diff) | |
| download | linux-next-1d9bb9c870632adea249cfdec49ac37e6f069164.tar.gz linux-next-1d9bb9c870632adea249cfdec49ac37e6f069164.zip | |
pinctrl: single: free the IRQ on domain creation failure
pcs_irq_init_chained_handler() requests a shared IRQ on affected SoCs, but
its domain creation failure path only removes a chained handler. That does
not release the action installed by request_irq(). The probe can continue
without interrupt support while leaving the shared IRQ action registered.
Use pcs_irq_free() to undo the appropriate type of handler registration.
At this point pcs->domain is NULL, so the helper only releases the parent
IRQ handler. Then mark the IRQ invalid, as the other initialization error
paths already do, to prevent another release from a later probe unwind or
remove.
This issue was identified during our ongoing static-analysis research while
reviewing kernel code.
Fixes: 3e6cee1786a1 ("pinctrl: single: Add support for wake-up interrupts")
Cc: stable@vger.kernel.org
Assisted-by: LLM
Co-developed-by: Ijae Kim <ae878000@gmail.com>
Signed-off-by: Ijae Kim <ae878000@gmail.com>
Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
Signed-off-by: Linus Walleij <linusw@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
