From: syzbot <syzbot+09d51a30df9fe76edb2a@syzkaller.appspotmail.com>
To: davem@davemloft.net, fweisbec@gmail.com, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, mingo@kernel.org,
netdev@vger.kernel.org, sbrivio@redhat.com, sd@queasysnail.net,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
yoshfuji@linux-ipv6.org
Subject: Re: KASAN: slab-out-of-bounds Read in tick_sched_handle
Date: Sat, 16 Mar 2019 07:49:01 -0700 [thread overview]
Message-ID: <00000000000093e58e0584374110@google.com> (raw)
In-Reply-To: <000000000000551b80057d31a5f7@google.com>
syzbot has bisected this bug to:
commit b8a51b38e4d4dec3e379d52c0fe1a66827f7cf1e
Author: Stefano Brivio <sbrivio@redhat.com>
Date: Thu Nov 8 11:19:23 2018 +0000
fou, fou6: ICMP error handlers for FoU and GUE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16f943e7200000
start commit: b8a51b38 fou, fou6: ICMP error handlers for FoU and GUE
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=15f943e7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=11f943e7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=b05cfdb4ee8ab9b2
dashboard link: https://syzkaller.appspot.com/bug?extid=09d51a30df9fe76edb2a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17359fab400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154a2a37400000
Reported-by: syzbot+09d51a30df9fe76edb2a@syzkaller.appspotmail.com
Fixes: b8a51b38 ("fou, fou6: ICMP error handlers for FoU and GUE")
next parent reply other threads:[~2019-03-16 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000551b80057d31a5f7@google.com>
2019-03-16 14:49 ` syzbot [this message]
2019-03-16 15:52 ` KASAN: slab-out-of-bounds Read in tick_sched_handle Stefano Brivio
2019-03-16 16:07 ` Dmitry Vyukov
2019-03-16 16:22 ` Stefano Brivio
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=00000000000093e58e0584374110@google.com \
--to=syzbot+09d51a30df9fe76edb2a@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=yoshfuji@linux-ipv6.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).