linux-kernel - Re: [PATCH][BLUETOOTH] add HCI_BROKEN_ISOC for 0e5e:6622 (bugzilla #9027)

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]

Date:	Thu, 14 Feb 2008 00:07:38 +0800
From:	SDiZ <sdiz@...z.net>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	SDiZ <sdiz@...z.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][BLUETOOTH] add HCI_BROKEN_ISOC for 0e5e:6622 (bugzilla
 #9027)

Marcel Holtmann wrote:
> Hi,
>
>   
>>>> This patch fix bugzilla #9027.
>>>> ``Syslog flooded with "hci_scodata_packet: hci0 SCO packet for unknown
>>>> connection handle 92" message"
>>>>
>>>> see http://bugzilla.kernel.org/show_bug.cgi?id=9027
>>>>     
>>>>         
>>> when we get the content of /proc/bus/usb/devices for this one. Do you
>>> have the manufacturer name of it or at least an idea which kind of
>>> device this is. Check "hciconfig hci0 version".
>>>   
>>>       
>> It have no text on the chips and package, so I don't know the
>> manufacturer name.
>>     
>
> and what about "hciconfig hci0 version"?
>   
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
HCI Ver: 2.0 (0x3) HCI Rev: 0x1f4 LMP Ver: 2.0 (0x3) LMP Subver: 0x1f4
Manufacturer: CONWISE Technology Corporation Ltd (66)
>> /proc/bus/usb/devices shows:
>>
>>
>> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
>> D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=16 #Cfgs= 1
>> P: Vendor=0e5e ProdID=6622 Rev= 1.34
>> C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
>> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
>> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
>> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>> I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
>> I:* If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
>>     
>
> That is not all. Otherwise it is violating the Bluetooth HCI USB
> specification and we have bigger problems when switching USB alternate
> endpoints.
>   
hmm.. there are some entries for usb mouse and hubs, nothing else.
I have attached the whole file for your reference.

Other then the annoying syslog message, everything work fine.
> Regards
>
> Marcel
>
>
>   

Regards,
Yuk-Pong, Cheng (SDiZ)




View attachment "usb-device.txt" of type "text/plain" (3582 bytes)