From mboxrd@z Thu Jan 1 00:00:00 1970 From: syzbot Subject: kernel panic: stack is corrupted in pointer Date: Wed, 17 Jul 2019 01:58:07 -0700 Message-ID: <0000000000001a51c4058ddcb1b6@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Return-path: Sender: linux-kernel-owner@vger.kernel.org To: airlied@linux.ie, alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org, ast@kernel.org, christian.koenig@amd.com, daniel@iogearbox.net, david1.zhou@amd.com, dri-devel@lists.freedesktop.org, leo.liu@amd.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com List-Id: amd-gfx.lists.freedesktop.org Hello, syzbot found the following crash on: HEAD commit: 1438cde7 Add linux-next specific files for 20190716 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=13988058600000 kernel config: https://syzkaller.appspot.com/x/.config?x=3430a151e1452331 dashboard link: https://syzkaller.appspot.com/bug?extid=79f5f028005a77ecb6bb compiler: gcc (GCC) 9.0.0 20181231 (experimental) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111fc8afa00000 The bug was bisected to: commit 96a5d8d4915f3e241ebb48d5decdd110ab9c7dcf Author: Leo Liu Date: Fri Jul 13 15:26:28 2018 +0000 drm/amdgpu: Make sure IB tests flushed after IP resume bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a46200600000 final crash: https://syzkaller.appspot.com/x/report.txt?x=16a46200600000 console output: https://syzkaller.appspot.com/x/log.txt?x=12a46200600000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com Fixes: 96a5d8d4915f ("drm/amdgpu: Make sure IB tests flushed after IP resume") Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: pointer+0x702/0x750 lib/vsprintf.c:2187 Shutting down cpus with NMI Kernel Offset: disabled --- This bug is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches