From: syzbot <syzbot+2990ca6e76c080858a9c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, glider@google.com, hpa@zytor.com,
jpoimboe@redhat.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, mbenes@suse.cz,
mhiramat@kernel.org, mingo@redhat.com, netdev@vger.kernel.org,
rostedt@goodmis.org, rppt@linux.ibm.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: KASAN: stack-out-of-bounds Read in update_stack_state
Date: Fri, 20 Dec 2019 00:14:01 -0800 [thread overview]
Message-ID: <000000000000a3c3ef059a1e4260@google.com> (raw)
In-Reply-To: <001a1143e62e6f71d20565bf329f@google.com>
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
next parent reply other threads:[~2019-12-20 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1143e62e6f71d20565bf329f@google.com>
2019-12-20 8:14 ` syzbot [this message]
2019-12-21 1:38 ` KASAN: stack-out-of-bounds Read in update_stack_state Steven Rostedt
2019-12-21 7:41 ` Dmitry Vyukov
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=000000000000a3c3ef059a1e4260@google.com \
--to=syzbot+2990ca6e76c080858a9c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@linux.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).