From: Dmitry Vyukov <dvyukov@google.com> To: syzbot <syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com>, John Fastabend <john.fastabend@gmail.com>, bpf <bpf@vger.kernel.org> Cc: David Airlie <airlied@linux.ie>, alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org, Alexei Starovoitov <ast@kernel.org>, christian.koenig@amd.com, Daniel Borkmann <daniel@iogearbox.net>, david1.zhou@amd.com, DRI <dri-devel@lists.freedesktop.org>, leo.liu@amd.com, LKML <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>, syzkaller-bugs <syzkaller-bugs@googlegroups.com> Subject: Re: kernel panic: stack is corrupted in pointer Date: Tue, 23 Jul 2019 09:38:56 +0200 [thread overview] Message-ID: <CACT4Y+ZGwKP+f4esJdx60AywO9b3Y5Bxb4zLtH6EEkaHpP6Zag@mail.gmail.com> (raw) In-Reply-To: <0000000000001a51c4058ddcb1b6@google.com> On Wed, Jul 17, 2019 at 10:58 AM syzbot <syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com> 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. #syz dup: kernel panic: corrupted stack end in dput > The bug was bisected to: > > commit 96a5d8d4915f3e241ebb48d5decdd110ab9c7dcf > Author: Leo Liu <leo.liu@amd.com> > 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
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Vyukov <dvyukov@google.com> To: syzbot <syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com>, John Fastabend <john.fastabend@gmail.com>, bpf <bpf@vger.kernel.org> Cc: David Airlie <airlied@linux.ie>, alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org, Alexei Starovoitov <ast@kernel.org>, christian.koenig@amd.com, Daniel Borkmann <daniel@iogearbox.net>, david1.zhou@amd.com, DRI <dri-devel@lists.freedesktop.org>, leo.liu@amd.com, LKML <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>, syzkaller-bugs <syzkaller-bugs@googlegroups.com> Subject: Re: kernel panic: stack is corrupted in pointer Date: Tue, 23 Jul 2019 09:38:56 +0200 [thread overview] Message-ID: <CACT4Y+ZGwKP+f4esJdx60AywO9b3Y5Bxb4zLtH6EEkaHpP6Zag@mail.gmail.com> (raw) In-Reply-To: <0000000000001a51c4058ddcb1b6@google.com> On Wed, Jul 17, 2019 at 10:58 AM syzbot <syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com> 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. #syz dup: kernel panic: corrupted stack end in dput > The bug was bisected to: > > commit 96a5d8d4915f3e241ebb48d5decdd110ab9c7dcf > Author: Leo Liu <leo.liu@amd.com> > 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
next prev parent reply other threads:[~2019-07-23 7:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-17 8:58 kernel panic: stack is corrupted in pointer syzbot 2019-07-23 7:38 ` Dmitry Vyukov [this message] 2019-07-23 7:38 ` Dmitry Vyukov 2019-07-23 17:26 ` John Fastabend 2019-07-23 17:26 ` syzbot 2019-07-23 17:26 ` syzbot 2019-07-23 17:33 ` John Fastabend 2019-07-23 17:33 ` John Fastabend 2019-07-24 1:40 ` syzbot 2019-07-24 8:30 ` Dmitry Vyukov 2019-07-24 16:22 ` John Fastabend
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CACT4Y+ZGwKP+f4esJdx60AywO9b3Y5Bxb4zLtH6EEkaHpP6Zag@mail.gmail.com \ --to=dvyukov@google.com \ --cc=airlied@linux.ie \ --cc=alexander.deucher@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=ast@kernel.org \ --cc=bpf@vger.kernel.org \ --cc=christian.koenig@amd.com \ --cc=daniel@iogearbox.net \ --cc=david1.zhou@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=john.fastabend@gmail.com \ --cc=leo.liu@amd.com \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com \ --cc=syzkaller-bugs@googlegroups.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.