linux-kernel - Re: bluetooth issues since kernel 6.4 - not discovering other bt devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAH7-e5unq6ggNjVkSsriUAmpvk4s7-NCYJrZnLK_3BjFO_Dceg@mail.gmail.com>
Date:   Tue, 3 Oct 2023 18:10:46 +0200
From:   Erik Dobák <erik.dobak@...il.com>
To:     Tomasz Moń <tomasz.mon@...dicsemi.no>
Cc:     Bagas Sanjaya <bagasdotme@...il.com>,
        Linux Stable <stable@...r.kernel.org>,
        Linux Bluetooth <linux-bluetooth@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Mediatek <linux-mediatek@...ts.infradead.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Luiz Augusto von Dentz <luiz.dentz@...il.com>,
        Matthias Brugger <matthias.bgg@...il.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>
Subject: Re: bluetooth issues since kernel 6.4 - not discovering other bt
 devices - /linux/drivers/bluetooth/btusb.c

Sorry Tomasz,

that must have been a reality glitch with your commit (cant find the
page refering to your commit now). But yes it is probably a kernel bug
as it manifests kernels 6.4 and not in the 6.1 LTS version.

Yours

E

On Tue, 3 Oct 2023 at 15:08, Tomasz Moń <tomasz.mon@...dicsemi.no> wrote:
>
> On Tue, 2023-10-03 at 14:42 +0200, Erik Dobák wrote:
> > Sure here you go:
> >
> > # lsusb -d 04c5:1670 -v
> >
> > Bus 001 Device 004: ID 04c5:1670 Fujitsu, Ltd Bluetooth Radio
> > Device Descriptor:
> >   bLength                18
> >   bDescriptorType         1
> >   bcdUSB               1.00
> >   bDeviceClass          224 Wireless
> >   bDeviceSubClass         1 Radio Frequency
> >   bDeviceProtocol         1 Bluetooth
> >   bMaxPacketSize0        64
> >   idVendor           0x04c5 Fujitsu, Ltd
> >   idProduct          0x1670
> >   bcdDevice            0.00
> >   iManufacturer           1 Realtek
> >   iProduct                2 Bluetooth Radio
> >   iSerial                 3 00e04c000001
> >   bNumConfigurations      1
> >   Configuration Descriptor:
> >     bLength                 9
> >     bDescriptorType         2
> >     wTotalLength       0x00b1
> >     bNumInterfaces          2
> >     bConfigurationValue     1
> >     iConfiguration          0
> >     bmAttributes         0xe0
> >       Self Powered
> >       Remote Wakeup
> >     MaxPower              500mA
> >     Interface Descriptor:
> >       bLength                 9
> >       bDescriptorType         4
> >       bInterfaceNumber        0
> >       bAlternateSetting       0
> >       bNumEndpoints           3
> >       bInterfaceClass       224 Wireless
> >       bInterfaceSubClass      1 Radio Frequency
> >       bInterfaceProtocol      1 Bluetooth
> >       iInterface              4 Bluetooth Radio
>
> I have no idea why you referred to my commits, i.e. c13380a55522
> ("Bluetooth: btusb: Do not require hardcoded interface numbers") later
> fixed by eaac6e223a0d ("Bluetooth: btusb: Fix bluetooth on Intel
> Macbook 2014") in the first place.
>
> BTUSB_IFNUM_2 is not even getting set for this device and therefore the
> patches have no impact on your issue. If you were affected, like the
> Intel Macbook 2014 was, then bear in mind that the issue would manifest
> as btusb driver not even binding to the device. From your emails
> however it appears that the issue is something different.
>
> I honestly don't think it has anything to do with my patches. If you
> know a Linux version where your bluetooth device works, then the next
> step would be to bisect to find the first bad commit.
>
> Best Regards,
> Tomasz Moń