Hi everyone!
On 08.02.24 16:32, syzbot wrote:
syzbot has bisected this issue to:
commit 456561ba8e495e9320c1f304bf1cd3d1043cbe7b
Author: Jonas Dreßler <verdre@xxxxxxx>
Date: Tue Feb 6 11:08:13 2024 +0000
Bluetooth: hci_conn: Only do ACL connections sequentially
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154f8550180000
start commit: b1d3a0e70c38 Add linux-next specific files for 20240208
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=174f8550180000
console output: https://syzkaller.appspot.com/x/log.txt?x=134f8550180000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb693ba195662a06
dashboard link: https://syzkaller.appspot.com/bug?extid=3f0a39be7a2035700868
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d95147e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=107c2d8fe80000
Reported-by: syzbot+3f0a39be7a2035700868@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: 456561ba8e49 ("Bluetooth: hci_conn: Only do ACL connections sequentially")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Hmm, looking at the backtraces, I think the issue that the introduction of the
sequential connect has introduced another async case: In hci_connect_acl(), when
we call hci_acl_create_connection_sync(), the conn state no longer immediately
gets set to BT_CONNECT, but remains in BT_OPEN or BT_CLOSED until the hci_sync
queue actually executes __hci_acl_create_connection_sync().
This means that now hci_connect_acl() is happy to do multiple
hci_acl_create_connection_sync calls, and the hci_sync machinery will happily
execute them right after each other. Then the newly introduced hci_abort_conn_sync()
in __hci_acl_create_connection_sync() calls hci_conn_del() and frees the conn
object, so the second time we enter __hci_acl_create_connection_sync(),
things blow up.
It looks to me like in theory the hci_connect_le_sync() logic is prone to a
similar issue, but in practice that's prohibited because in hci_connect_le_sync()
we lookup whether the conn object still exists and bail out if it doesn't.
Even for LE though I think we can queue multiple hci_connect_le_sync() calls
and those will happily send HCI_OP_LE_CREATE_CONN no matter what the connection
state actually is?
So assuming this analysis is correct, what do we do to fix this? It seems to me
that
1) we want a BT_CONNECT_QUEUED state for connections, so that the state
machine covers this additional stage that we have for ACL and LE connections now.
2) the conn object can still disappear while the __hci_acl_create_connection_sync()
is queued, so we need something like the "if conn doesn't exist anymore, bail out"
check from hci_connect_le_sync() in __hci_acl_create_connection_sync(), too.
That said, the current check in hci_connect_le_sync() that's using the connection
handle to lookup the conn does not seem great, aren't these handles re-used
after connections are torn down?
Cheers,
Jonas
