lkml.org 
[lkml]   [2020]   [Dec]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 5.10 00/40] 5.10.3-rc1 review
From
Date
On 12/28/20 1:50 AM, Pavel Machek wrote:
> Hi!
>
>>>>>>> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
>>>>>>> or in the git tree and branch at:
>>>>>>>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/
>>>>>>> linu
>>>>>>> x-
>>>>>>> stable-rc.git linux-5.10.y
>>>>>>> and the diffstat can be found below.
>>>>>>>
>>>>>>> thanks,
>>>>>>>
>>>>>>> greg k-h
>>>>>>
>>>>>> hello ,
>>>>>> Compiled and booted 5.10.3-rc1+.
>>>>>>
>>>>>> dmesg -l err gives...
>>>>>> --------------x-------------x------------------->
>>>>>>    43.190922] Bluetooth: hci0: don't support firmware rome
>>>>>> 0x31010100
>>>>>> --------------x---------------x----------------->
>>>>>>
>>>>>> My Bluetooth is Off.
>>>>>
>>>>> Is this a new warning?  Does it show up on 5.10.2?
>>>>>
>>>>>> Tested-by: Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
>>>>>
>>>>> thanks for testing?
>>>>>
>>>>> greg k-h
>>>>
>>>> this does not show up in 5.10.2-rc1+
>>>
>>> Odd.  Can you run 'git bisect' to find the offending commit?
>>>
>>> Does this same error message show up in Linus's git tree?
>
>> i will try to do "git bisect" . i saw this error in linus's tree.
>
> The bug is in -stable, too, so it is probably easiest to do bisect on
> -stable tree. IIRC there's less then few hundred commits, so it should
> be feasible to do bisection by hand if you are not familiar with git
> bisect.
>

My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab-out-of-bounds
read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong
with it unless some BT device sends a bad report which used to be accepted
but is now silently ignored.

Guenter

[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2020-12-29 00:08    [W:0.087 / U:0.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site