On Wed, 26 Jul 2023 at 18:09, Aleksandr Nogikh <nogikh@xxxxxxxxxx> wrote: > > On Wed, Jul 26, 2023 at 5:03 PM syzbot > <syzbot+3f6a670108ce43356017@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > syzbot suspects this issue was fixed by commit: > > > > commit 41a37d157a613444c97e8f71a5fb2a21116b70d7 > > Author: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > > Date: Mon Dec 26 04:21:51 2022 +0000 > > > > arm64: dts: qcom: qcs404: use symbol names for PCIe resets > > > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b48111a80000 > > start commit: [unknown] > > git tree: upstream > > kernel config: https://syzkaller.appspot.com/x/.config?x=fe56f7d193926860 > > dashboard link: https://syzkaller.appspot.com/bug?extid=3f6a670108ce43356017 > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1209f878c80000 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111a48ab480000 > > > > If the result looks correct, please mark the issue as fixed by replying with: > > No, it's quite unlikely. I highly suspect that the bisect was wrong here. The only thing that was changed by the mentioned commit is the device tree for the pretty obscure platform, which is not 'Google Compute Engine'. > > > > > #syz fix: arm64: dts: qcom: qcs404: use symbol names for PCIe resets > > > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection -- With best wishes Dmitry
