summaryrefslogtreecommitdiff
path: root/tools/lib/python/feat
diff options
context:
space:
mode:
authorSergey Shtylyov <s.shtylyov@auroraos.dev>2026-06-01 23:21:30 +0300
committerLuiz Augusto von Dentz <luiz.von.dentz@intel.com>2026-06-11 21:24:41 +0300
commit93f5d7057da83e951e1e49de7c8a80ccd44d8d82 (patch)
tree0a054b60f50ce674d6c0389c1cfaca5424acd492 /tools/lib/python/feat
parent43ea69d0ef06975837e7d7270b64f4b500113837 (diff)
downloadlinux-93f5d7057da83e951e1e49de7c8a80ccd44d8d82.tar.xz
Bluetooth: hci_h5: reset hci_uart::priv in the close() method
Unlike the other HCI UART drivers, the 3-wire UART driver doesn't reset hci_uart::priv in its close() method -- this shouldn't pose a problem as all the methods in *struct* hci_uart_proto should only be called after the open() method that sets up hci_uart::priv properly. However, it seems wise to be more consistent and provide for the *struct* hci_uart_proto methods the same state that exists before the first open() method call (so that they rather crash than dereference a stale hci_uart::priv pointer)... Found by Linux Verification Center (linuxtesting.org) with the Svace static analysis tool. Signed-off-by: Sergey Shtylyov <s.shtylyov@auroraos.dev> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'tools/lib/python/feat')
0 files changed, 0 insertions, 0 deletions