On Thu, Apr 9, 2020 at 7:28 AM <daniels@xxxxxxxxxxxxx> wrote:
>
> From: Daniels Umanovskis <du@xxxxxxxxxx>
>
> The error could indicate a problem with the Bluetooth device. It
> is easier to investigate if the packet's actual length gets logged,
> not just the fact that a discrepancy occurred.
>
> Signed-off-by: Daniels Umanovskis <du@xxxxxxxxxx>
> ---
> net/bluetooth/hci_event.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 0a591be8b0ae..af7fa7ef94ed 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -5353,7 +5353,8 @@ static void process_adv_report(struct hci_dev *hdev, u8 type, bdaddr_t *bdaddr,
>
> /* Adjust for actual length */
> if (len != real_len) {
> - bt_dev_err_ratelimited(hdev, "advertising data len corrected");
> + bt_dev_err_ratelimited(hdev, "advertising data len corrected %u -> %u",
> + len, real_len);
> len = real_len;
> }
>
> --
> 2.20.1
>
Reviewed-by: Alain Michaud <alainm@xxxxxxxxxxxx>
