diff options
| author | Guangshuo Li <lgs201920130244@gmail.com> | 2026-08-08 13:15:32 +0800 |
|---|---|---|
| committer | Luiz Augusto von Dentz <luiz.von.dentz@intel.com> | 2026-08-11 15:40:05 -0400 |
| commit | 32b42c0704fddf56809d9107a8061a367ceb8aa0 (patch) | |
| tree | f6b878ae4b5e16922eaa305bad92d3784cb9b501 /scripts/objdiff | |
| parent | 809a66378e9e087481799de508990f606a79ccc4 (diff) | |
| download | linux-next-32b42c0704fddf56809d9107a8061a367ceb8aa0.tar.gz linux-next-32b42c0704fddf56809d9107a8061a367ceb8aa0.zip | |
Bluetooth: hci_bcm: fix usage_count leak when autosuspend_delay is negative
bcm_request_irq() calls pm_runtime_use_autosuspend(), but bcm_close()
does not call the matching pm_runtime_dont_use_autosuspend() when
tearing down 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 driver 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: e88ab30d3669 ("Bluetooth: hci_bcm: Add suspend/resume runtime PM functions")
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