diff options
| author | Guangshuo Li <lgs201920130244@gmail.com> | 2026-08-08 13:30:57 +0800 |
|---|---|---|
| committer | Luiz Augusto von Dentz <luiz.von.dentz@intel.com> | 2026-08-11 15:40:09 -0400 |
| commit | bc2791e60e0829e15a6f312006f4a667426deaf6 (patch) | |
| tree | 1b79f7c1aba84bc1df91dd8ea40c59cb5cd8a064 /scripts/objdiff | |
| parent | 9e257e3586428be74ca545affc4f0b8d679b3a77 (diff) | |
| download | linux-next-bc2791e60e0829e15a6f312006f4a667426deaf6.tar.gz linux-next-bc2791e60e0829e15a6f312006f4a667426deaf6.zip | |
Bluetooth: hci_intel: fix usage_count leak when autosuspend_delay is negative
intel_set_power() calls pm_runtime_use_autosuspend() when powering on
the device, but the power-off path does not call the matching
pm_runtime_dont_use_autosuspend() before disabling runtime PM.
If the autosuspend delay is set to a negative value while autosuspend
is enabled, the runtime PM core increments usage_count to prevent
runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
during teardown, this reference is not dropped and usage_count remains
unbalanced.
Add the missing pm_runtime_dont_use_autosuspend() call before disabling
runtime PM.
This issue was found by manual code inspection.
Fixes: 74cdad37cd24 ("Bluetooth: hci_intel: Add runtime PM support")
Cc: stable@vger.kernel.org
Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions