diff options
| author | Guangshuo Li <lgs201920130244@gmail.com> | 2026-08-08 13:26:54 +0800 |
|---|---|---|
| committer | Luiz Augusto von Dentz <luiz.von.dentz@intel.com> | 2026-08-11 15:40:07 -0400 |
| commit | 9e257e3586428be74ca545affc4f0b8d679b3a77 (patch) | |
| tree | dbd000af16c8b43807097c9d6f3aedcb84ce22fd /scripts/objdiff | |
| parent | 32b42c0704fddf56809d9107a8061a367ceb8aa0 (diff) | |
| download | linux-next-9e257e3586428be74ca545affc4f0b8d679b3a77.tar.gz linux-next-9e257e3586428be74ca545affc4f0b8d679b3a77.zip | |
Bluetooth: hci_h5: fix usage_count leak when autosuspend_delay is negative
h5_btrtl_open() calls pm_runtime_use_autosuspend(), but
h5_btrtl_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: d9dd833cf6d2 ("Bluetooth: hci_h5: Add runtime suspend")
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