From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D3ED4C76186 for ; Tue, 23 Jul 2019 17:26:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B1FAE218B0 for ; Tue, 23 Jul 2019 17:26:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391084AbfGWR0d (ORCPT ); Tue, 23 Jul 2019 13:26:33 -0400 Received: from mail-io1-f71.google.com ([209.85.166.71]:54113 "EHLO mail-io1-f71.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391063AbfGWR03 (ORCPT ); Tue, 23 Jul 2019 13:26:29 -0400 Received: by mail-io1-f71.google.com with SMTP id h3so47979465iob.20 for ; Tue, 23 Jul 2019 10:26:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:in-reply-to:message-id:subject :from:to:cc; bh=18dpD/naihNOjoNrgGIrjwwIJhV9RriEpPtRMJT/ORo=; b=eHMEJtFBkoGiIHNG3BdvLB37dUfQG9lYUlTZW8h9dGhKew4nPycmpRKoVOtAC3J0be ICl0d4SelomhNI8Lt+f1XRl6Ncj0lj75+Ntx0hySR6CHokA3yD3TcVBwt0hII6f9xtB9 /ePBv/x61Z/7z4/5oLCyXcl4dHsmOHus/hEAMZuCjS46BXVIjmD4j3CmDr42GsNfX5JK r0IMKC7va73YoXJhmq4i9yOUnV7EW5U83iymon+B86nuf6LBvzx6ZziLgN42P8AKewTM 2VyA9D0rT10VcM3S1esPK3qIQRdVg/LQUmcvh0qWidipEY57mJ1WVjJKzXvk+b67A0jK FkmA== X-Gm-Message-State: APjAAAVQwqgDQE+X/B04cNFaXHvFO/iIQyfUEhDDW5IbS3BY6j7R43ZF X5CGgJUSBdmuPuw0JvG3xxNI/mjIJrTx/J9fZWmK7re8hOEf X-Google-Smtp-Source: APXvYqyCe7AfPrluXBIbZlQzVEeh9JxvWJ4U1jT02MrsCAmY9jj6X4SXKsEfnTom19bvNkP5FIZFgnFlrHkpQva5F/PA/CCuwooO MIME-Version: 1.0 X-Received: by 2002:a5d:9acf:: with SMTP id x15mr44816852ion.190.1563902788559; Tue, 23 Jul 2019 10:26:28 -0700 (PDT) Date: Tue, 23 Jul 2019 10:26:28 -0700 In-Reply-To: <5d37433a832d_3aba2ae4f6ec05bc3a@john-XPS-13-9370.notmuch> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000002cec2e058e5c7e63@google.com> Subject: Re: Re: kernel panic: stack is corrupted in pointer From: syzbot To: John Fastabend Cc: airlied@linux.ie, alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org, ast@kernel.org, bpf@vger.kernel.org, christian.koenig@amd.com, daniel@iogearbox.net, david1.zhou@amd.com, dri-devel@lists.freedesktop.org, dvyukov@google.com, john.fastabend@gmail.com, leo.liu@amd.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Dmitry Vyukov wrote: >> On Wed, Jul 17, 2019 at 10:58 AM syzbot >> wrote: >> > >> > 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 >> From the repro it looks like the same bpf stack overflow bug. +John >> We need to dup them onto some canonical report for this bug, or this >> becomes unmanageable. > Fixes in bpf tree should fix this. Hopefully, we will squash this once > fixes > percolate up. > #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git ">" does not look like a valid git branch or commit. >> #syz dup: kernel panic: corrupted stack end in dput >> > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: syzbot Subject: Re: Re: kernel panic: stack is corrupted in pointer Date: Tue, 23 Jul 2019 10:26:28 -0700 Message-ID: <0000000000002cec2e058e5c7e63@google.com> References: <5d37433a832d_3aba2ae4f6ec05bc3a@john-XPS-13-9370.notmuch> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Return-path: In-Reply-To: <5d37433a832d_3aba2ae4f6ec05bc3a@john-XPS-13-9370.notmuch> Sender: linux-kernel-owner@vger.kernel.org Cc: airlied@linux.ie, alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org, ast@kernel.org, bpf@vger.kernel.org, christian.koenig@amd.com, daniel@iogearbox.net, david1.zhou@amd.com, dri-devel@lists.freedesktop.org, dvyukov@google.com, john.fastabend@gmail.com, leo.liu@amd.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com List-Id: dri-devel@lists.freedesktop.org > Dmitry Vyukov wrote: >> On Wed, Jul 17, 2019 at 10:58 AM syzbot >> wrote: >> > >> > 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 >> From the repro it looks like the same bpf stack overflow bug. +John >> We need to dup them onto some canonical report for this bug, or this >> becomes unmanageable. > Fixes in bpf tree should fix this. Hopefully, we will squash this once > fixes > percolate up. > #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git ">" does not look like a valid git branch or commit. >> #syz dup: kernel panic: corrupted stack end in dput >> > 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