netdev - Re: Re: kernel panic: stack is corrupted in pointer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 23 Jul 2019 10:33:51 -0700
From:   John Fastabend <john.fastabend@...il.com>
To:     syzbot <syzbot+79f5f028005a77ecb6bb@...kaller.appspotmail.com>,
        John Fastabend <john.fastabend@...il.com>
Cc:     airlied@...ux.ie, alexander.deucher@....com,
        amd-gfx@...ts.freedesktop.org, ast@...nel.org, bpf@...r.kernel.org,
        christian.koenig@....com, daniel@...earbox.net,
        david1.zhou@....com, dri-devel@...ts.freedesktop.org,
        dvyukov@...gle.com, john.fastabend@...il.com, leo.liu@....com,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: Re: kernel panic: stack is corrupted in pointer

syzbot wrote:
> > Dmitry Vyukov wrote:
> >> On Wed, Jul 17, 2019 at 10:58 AM syzbot
> >> <syzbot+79f5f028005a77ecb6bb@...kaller.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.
> 
> > 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.
> 

try again,

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master