From: syzbot <syzbot+621fd33c0b53d15ee8de@syzkaller.appspotmail.com>
To: davem@davemloft.net, jhs@mojatatu.com, jiri@resnulli.us,
kuba@kernel.org, leandro.maciel.dorileo@intel.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vedang.patel@intel.com,
xiyou.wangcong@gmail.com
Subject: Re: KASAN: use-after-free Read in dump_schedule
Date: Fri, 04 Sep 2020 02:17:08 -0700 [thread overview]
Message-ID: <000000000000427d4405ae795514@google.com> (raw)
In-Reply-To: <000000000000a358f905ae6b5dc6@google.com>
syzbot has bisected this issue to:
commit 7b9eba7ba0c1b24df42b70b62d154b284befbccf
Author: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
Date: Mon Apr 8 17:12:17 2019 +0000
net/sched: taprio: fix picos_per_byte miscalculation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15464af9900000
start commit: fc3abb53 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17464af9900000
console output: https://syzkaller.appspot.com/x/log.txt?x=13464af9900000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1c560d0f4e121c9
dashboard link: https://syzkaller.appspot.com/bug?extid=621fd33c0b53d15ee8de
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1129d0e9900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17fb6a25900000
Reported-by: syzbot+621fd33c0b53d15ee8de@syzkaller.appspotmail.com
Fixes: 7b9eba7ba0c1 ("net/sched: taprio: fix picos_per_byte miscalculation")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-04 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 16:37 KASAN: use-after-free Read in dump_schedule syzbot
2020-09-04 9:17 ` syzbot [this message]
2021-01-22 17:21 ` syzbot
2021-01-25 9:35 ` 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=000000000000427d4405ae795514@google.com \
--to=syzbot+621fd33c0b53d15ee8de@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leandro.maciel.dorileo@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vedang.patel@intel.com \
--cc=xiyou.wangcong@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.