* Re: KASAN: stack-out-of-bounds Read in update_stack_state [not found] <001a1143e62e6f71d20565bf329f@google.com> @ 2019-12-20 8:14 ` syzbot 2019-12-21 1:38 ` Steven Rostedt 0 siblings, 1 reply; 3+ messages in thread From: syzbot @ 2019-12-20 8:14 UTC (permalink / raw) To: akpm, glider, hpa, jpoimboe, keescook, linux-kernel, mbenes, mhiramat, mingo, netdev, rostedt, rppt, syzkaller-bugs, tglx, x86 syzbot suspects this bug was fixed by commit: commit 4ee7c60de83ac01fa4c33c55937357601631e8ad Author: Steven Rostedt (VMware) <rostedt@goodmis.org> 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: KASAN: stack-out-of-bounds Read in update_stack_state 2019-12-20 8:14 ` KASAN: stack-out-of-bounds Read in update_stack_state syzbot @ 2019-12-21 1:38 ` Steven Rostedt 2019-12-21 7:41 ` Dmitry Vyukov 0 siblings, 1 reply; 3+ messages in thread From: Steven Rostedt @ 2019-12-21 1:38 UTC (permalink / raw) To: syzbot Cc: akpm, glider, hpa, jpoimboe, keescook, linux-kernel, mbenes, mhiramat, mingo, netdev, rppt, syzkaller-bugs, tglx, x86 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@syzkaller.appspotmail.com> wrote: > syzbot suspects this bug was fixed by commit: > > commit 4ee7c60de83ac01fa4c33c55937357601631e8ad > Author: Steven Rostedt (VMware) <rostedt@goodmis.org> > 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: KASAN: stack-out-of-bounds Read in update_stack_state 2019-12-21 1:38 ` Steven Rostedt @ 2019-12-21 7:41 ` Dmitry Vyukov 0 siblings, 0 replies; 3+ messages in thread From: Dmitry Vyukov @ 2019-12-21 7:41 UTC (permalink / raw) To: Steven Rostedt Cc: syzbot, Andrew Morton, Alexander Potapenko, H. Peter Anvin, Josh Poimboeuf, Kees Cook, LKML, mbenes, Masami Hiramatsu, Ingo Molnar, netdev, rppt, syzkaller-bugs, Thomas Gleixner, the arch/x86 maintainers On Sat, Dec 21, 2019 at 2:38 AM Steven Rostedt <rostedt@goodmis.org> wrote: > > > 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. There is a hundred of reports accumulated on dashboard for this bug report for past 2 years ;) > On Fri, 20 Dec 2019 00:14:01 -0800 > syzbot <syzbot+2990ca6e76c080858a9c@syzkaller.appspotmail.com> wrote: > > > syzbot suspects this bug was fixed by commit: > > > > commit 4ee7c60de83ac01fa4c33c55937357601631e8ad > > Author: Steven Rostedt (VMware) <rostedt@goodmis.org> > > 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 > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/20191220203847.08267447%40rorschach.local.home. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-12-21 7:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <001a1143e62e6f71d20565bf329f@google.com>
2019-12-20 8:14 ` KASAN: stack-out-of-bounds Read in update_stack_state syzbot
2019-12-21 1:38 ` Steven Rostedt
2019-12-21 7:41 ` Dmitry Vyukov
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).