Re: KASAN: stack-out-of-bounds Read in update_stack_state

[Steven Rostedt]

What's the actual bug? "stack-out-of-bounds" is rather useless without
any actual output dump. But that's besides the point, this commit is
*extremely* unlikely to be the culprit.

-- Steve


On Fri, 20 Dec 2019 00:14:01 -0800
syzbot <syzbot+2990ca6e76c080858a9c@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> syzbot suspects this bug was fixed by commit:
> 
> commit 4ee7c60de83ac01fa4c33c55937357601631e8ad
> Author: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx>
> Date:   Fri Mar 23 14:18:03 2018 +0000
> 
>      init, tracing: Add initcall trace events
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11ebd0aee00000
> start commit:   0b6b8a3d Merge branch 'bpf-misc-selftest-improvements'
> git tree:       bpf-next
> kernel config:  https://syzkaller.appspot.com/x/.config?x=82a189bf69e089b5
> dashboard link: https://syzkaller.appspot.com/bug?extid=2990ca6e76c080858a9c
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11dde5b3800000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1347b65d800000
> 
> If the result looks correct, please mark the bug fixed by replying with:
> 
> #syz fix: init, tracing: Add initcall trace events
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection