Hi Kuba,
> SCO packet reassembler may have a fragment of SCO packet, from
> previous connection, cached and not removed when SCO connection
> is ended. Packets from new SCO connection are then going to be
> attached to that fragment, creating an invalid SCO packets.
>
> Controllers like Intel's WilkinsPeak are always fragmenting
> SCO packet into 3 parts (#1, #2, #3). Packet #1 contains
> SCO header and audio data, others just audio data. if there is
> a fragment cached from previous connection, i.e. #1, first
> SCO packet from new connection is going to be attached to it
> creating packet consisting of fragments #1-#1-#2. This will
> be forwarded to upper layers. After that, fragment #3 is going
> to be used as a starting point for another SCO packet.
> It does not contain a SCO header, but the code expects it,
> casts a SCO header structure on it, and reads whatever audio
> data happens to be there as SCO packet length and handle.
> From that point on, we are assembling random data into SCO
> packets. Usually it recovers quickly as initial audio data
> usually contains mostly zeros (muted stream), but setups
> of over 4 seconds were observed.
> Issue manifests itself by printing on the console:
> Bluetooth: hci0 SCO packet for unknown connection handle 48
> Bluetooth: hci0 SCO packet for unknown connection handle 2560
> Bluetooth: hci0 SCO packet for unknown connection handle 12288
> It may also show random handles if audio data was non-zeroed.
> Hcidump shows SCO packets with random length and handles.
>
> Few messages with handle 0 at connection creation are OK
> for some controllers (like WilkinsPeak), as there are SCO packets
> with zeroed handle at the beginning (possible controller bug).
> Few of such messages at connection end, with a handle looking
> sane (around 256, 512, 768 ...) is also OK, as these are last
> SCO packets that were assembled and sent up, before connection
> was broken, but were not handled in time.
>
> Also, WilkinsPeak has an issue that sometimes, at SCO connection
> creation it does not send third fragment of first SCO packet
> (#1-#2-#1-#2-#3...). This is not fixed in this patch but manifests
> itself as this issue.
that should be fixed in the firmware and not in the driver actually.
> Signed-off-by: Kuba Pawlak <kubax.t.pawlak@xxxxxxxxx>
> ---
> drivers/bluetooth/btusb.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 9521b7bcc22d61b7690a928bc09500c883fe5495..3ba0397525069f12042f15170d0e96c5dedeaee7 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -1203,6 +1203,16 @@ static void btusb_notify(struct hci_dev *hdev, unsigned int evt)
> }
> }
>
> +static void btusb_remove_sco_frag(struct hci_dev *hdev)
> +{
> + struct btusb_data *data = hci_get_drvdata(hdev);
> +
> + spin_lock(&data->rxlock);
> + kfree_skb(data->sco_skb);
> + data->sco_skb = NULL;
> + spin_unlock(&data->rxlock);
> +}
Don't bother with this. It is easy enough to just keep this code inline. Same as with my pseudo-patch.
> +
> static inline int __set_isoc_interface(struct hci_dev *hdev, int altsetting)
> {
> struct btusb_data *data = hci_get_drvdata(hdev);
> @@ -1277,6 +1287,18 @@ static void btusb_work(struct work_struct *work)
> clear_bit(BTUSB_ISOC_RUNNING, &data->flags);
> usb_kill_anchored_urbs(&data->isoc_anchor);
>
> + /*
> + * When SCO connection is ended, a packet fragment
> + * may be left in reassembler. It would then be attached
> + * to SCO fragments of next SCO connection. Stream
> + * reassembly code will then read audio data as SCO packet
> + * headers creating wrongly reassembled SCO stream with
> + * packets of random length and handles.
> + * Clear all outstanding fragments when SCO connection
> + * is dropped.
> + */
Please use proper comment coding style.
And this is not only when SCO connection has been ended. This is when we are switching alternate settings. So the comment needs to read this properly. This will be triggered when switching from 0 connections to 1 connection, but also when switching from 1 connect to 2 connections. And of course the case you care, when dropping a connection.
> + btusb_remove_sco_frag(hdev);
> +
> if (__set_isoc_interface(hdev, new_alts) < 0)
> return;
> }
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
