[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANp29Y6T2sKnnTGtotraCX8saAUw1kSUhS-be=3GM_t+szZ-3Q@mail.gmail.com>
Date: Wed, 19 Jul 2023 10:45:07 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: syzbot <syzbot+c19afa60d78984711078@...kaller.appspotmail.com>,
davem@...emloft.net, hdanton@...a.com, jiri@...dia.com,
johan.hedberg@...il.com, linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org, luiz.dentz@...il.com,
marcel@...tmann.org, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl
On Tue, Jul 18, 2023 at 9:45 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Mon, 17 Jul 2023 13:22:24 -0700 syzbot wrote:
> > syzbot suspects this issue was fixed by commit:
> >
> > commit d772781964415c63759572b917e21c4f7ec08d9f
> > Author: Jakub Kicinski <kuba@...nel.org>
> > Date: Fri Jan 6 06:33:54 2023 +0000
> >
> > devlink: bump the instance index directly when iterating
>
> Hm, don't think so. It's not the first issue where syzbot decided
> this commit was the resolution. I wonder what makes it special.
Judging by the bisection log, the commit fixed some "INFO: rcu
detected stall in" error that was also triggerable by the reproducer.
Though for me it's not clear how exactly -- at least the reproducer
does not seem to be interacting with devlink..
--
Aleksandr
>
> --
Powered by blists - more mailing lists