* Re: [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl [not found] <00000000000049baa505e65e3939@google.com> @ 2023-07-17 20:22 ` syzbot 2023-07-18 19:45 ` Jakub Kicinski 0 siblings, 1 reply; 3+ messages in thread From: syzbot @ 2023-07-17 20:22 UTC (permalink / raw) To: davem, hdanton, jiri, johan.hedberg, kuba, linux-bluetooth, linux-kernel, luiz.dentz, marcel, netdev, syzkaller-bugs syzbot suspects this issue was fixed by commit: commit d772781964415c63759572b917e21c4f7ec08d9f Author: Jakub Kicinski <kuba@kernel.org> Date: Fri Jan 6 06:33:54 2023 +0000 devlink: bump the instance index directly when iterating bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=136a0414a80000 start commit: 84368d882b96 Merge tag 'soc-fixes-6.1-3' of git://git.kern.. git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=24d192d47d02d9e1 dashboard link: https://syzkaller.appspot.com/bug?extid=c19afa60d78984711078 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168fc765880000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1376e745880000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: devlink: bump the instance index directly when iterating For information about bisection process see: https://goo.gl/tpsmEJ#bisection ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl 2023-07-17 20:22 ` [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl syzbot @ 2023-07-18 19:45 ` Jakub Kicinski 2023-07-19 8:45 ` Aleksandr Nogikh 0 siblings, 1 reply; 3+ messages in thread From: Jakub Kicinski @ 2023-07-18 19:45 UTC (permalink / raw) To: syzbot Cc: davem, hdanton, jiri, johan.hedberg, linux-bluetooth, linux-kernel, luiz.dentz, marcel, netdev, syzkaller-bugs 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@kernel.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. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl 2023-07-18 19:45 ` Jakub Kicinski @ 2023-07-19 8:45 ` Aleksandr Nogikh 0 siblings, 0 replies; 3+ messages in thread From: Aleksandr Nogikh @ 2023-07-19 8:45 UTC (permalink / raw) To: Jakub Kicinski Cc: syzbot, davem, hdanton, jiri, johan.hedberg, linux-bluetooth, linux-kernel, luiz.dentz, marcel, netdev, syzkaller-bugs On Tue, Jul 18, 2023 at 9:45 PM Jakub Kicinski <kuba@kernel.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@kernel.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 > > -- ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-07-19 8:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <00000000000049baa505e65e3939@google.com>
2023-07-17 20:22 ` [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl syzbot
2023-07-18 19:45 ` Jakub Kicinski
2023-07-19 8:45 ` Aleksandr Nogikh
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).