Hi Linus,
Thank you for looking at the syzbot's email!
The bisection info was indeed included in this case by mistake. We have fixed this, now the bot should not mention bisections that point to release commits and thefefore won't be pinging you as the commit author.
Best Regards,
Aleksandr
On Sun, May 22, 2022 at 08:56PM -0700, Linus Torvalds wrote:
> On Sun, May 22, 2022 at 4:01 PM syzbot
> <syzbot+48135e34de22e3a82c99@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > The issue was bisected to:
> >
> > commit c470abd4fde40ea6a0846a2beab642a578c0b8cd
> > Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> > Date: Sun Feb 19 22:34:00 2017 +0000
> >
> > Linux 4.10
>
> Heh. That looks very unlikely, so the bisection seems to sadly have
> failed at some point.
>
> At least one of the KASAN reports (that "final oops") does look very
> much like the bug fixed by commit 1bff51ea59a9 ("Bluetooth: fix
> use-after-free error in lock_sock_nested()"), so this may already be
> fixed, but who knows...
>
> But that "update Makefile to 4.10" is not the cause...
>
> Linus
