From: syzbot <syzbot+999bca54de2ee169c021@syzkaller.appspotmail.com>
To: davem@davemloft.net, dvyukov@google.com, frederic@kernel.org,
fweisbec@gmail.com, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, mingo@kernel.org,
netdev@vger.kernel.org, sbrivio@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
yoshfuji@linux-ipv6.org
Subject: Re: KASAN: use-after-free Read in tick_sched_handle (3)
Date: Thu, 07 Nov 2019 05:42:07 -0800 [thread overview]
Message-ID: <000000000000e139ab0596c1d4c0@google.com> (raw)
In-Reply-To: <0000000000007829c8057b0b58ed@google.com>
syzbot suspects this bug was fixed by commit:
commit bc6e019b6ee65ff4ebf3ca272f774cf6c67db669
Author: Stefano Brivio <sbrivio@redhat.com>
Date: Thu Jan 3 20:43:34 2019 +0000
fou: Prevent unbounded recursion in GUE error handler also with UDP-Lite
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=119c0bc2600000
start commit: 1c7fc5cb Linux 5.0-rc2
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=817708c0a0300f84
dashboard link: https://syzkaller.appspot.com/bug?extid=999bca54de2ee169c021
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c95a30c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11df0107400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: fou: Prevent unbounded recursion in GUE error handler also with
UDP-Lite
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-07 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000007829c8057b0b58ed@google.com>
[not found] ` <20181120041041.GA3398@lerouge>
2018-11-20 4:42 ` KASAN: use-after-free Read in tick_sched_handle (3) Dmitry Vyukov
2019-11-07 13:42 ` syzbot [this message]
2019-11-08 12:51 ` 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=000000000000e139ab0596c1d4c0@google.com \
--to=syzbot+999bca54de2ee169c021@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=frederic@kernel.org \
--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=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).