[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X/Kz4KHxoU/YYEvu@kroah.com>
Date: Mon, 4 Jan 2021 07:21:20 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jeffrin Jose T <jeffrin@...agiritech.edu.in>
Cc: Guenter Roeck <linux@...ck-us.net>, Pavel Machek <pavel@...x.de>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, stable@...r.kernel.org
Subject: Re: [PATCH 5.10 00/40] 5.10.3-rc1 review
On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
> On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
> > 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/s
> > > > > > > > > table/
> > > > > > > > > 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@...agiritech.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
> >
> hello,
>
> Did "git bisect" in a typically ok fashion and found that 5.9.0 is
> working for bluetooth related. But 5.10.0-rc1 related is not working.
>
> some related information in bisect.txt attached.
>
> --
> software engineer
> rajagiri school of engineering and technology - autonomous
>
> $sudo git bisect bad
> Bisecting: 0 revisions left to test after this (roughly 1 step)
> [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds: Update devicetree documents for ID_RGB
>
> $sudo git bisect bad
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
That's really odd, as that commit only has a Makefile change.
Also, why run this as root?
greg k-h
Powered by blists - more mailing lists