Re: null pointer error in bluez kernel

[Marcel Holtmann <marcel@holtmann.org>]

Hi,

> When we test Bluetooth "out of range" case, occasionally we got kernel
> panic result. From the panic log we can see it was caused by NULL
> point error.
> 
> In one panic case, the NULL pointer happens at:
> 
> " if (sk->sk_state == BT_CONNECTED)" in the function
> l2cap_sock_sendmsg() of l2cap.c
> 
> In another panic case, the NULL pointer is at:
> 
> "parent->sk_data_ready(parent, 0);" in the function l2cap_conn_start()
> of l2cap.c
> 
> In a normal call sequence, these null pointer shall never happen,
> because it is already well considered. But it seems that the "out of
> range" test usually leads the unexpected call sequence which may
> randomly cause NULL pointer. Is there any way we can use to avoid the
> NULL pointer?

what kernel version is this? Never had this problem since the link
supervision timeout should trigger a HCI Disconnect.

Regards

Marcel