From: syzbot <syzbot+8971da381fb5a31f542d@syzkaller.appspotmail.com>
To: davem@davemloft.net, jhs@mojatatu.com, jiri@resnulli.us,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
vinicius.gomes@intel.com, xiyou.wangcong@gmail.com
Subject: Re: general protection fault in taprio_dequeue_soft
Date: Tue, 15 Dec 2020 09:38:02 -0800 [thread overview]
Message-ID: <000000000000753add05b6843897@google.com> (raw)
In-Reply-To: <000000000000bd226505b67d9989@google.com>
syzbot has bisected this issue to:
commit b5b73b26b3ca34574124ed7ae9c5ba8391a7f176
Author: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Date: Thu Sep 10 00:03:11 2020 +0000
taprio: Fix allowing too small intervals
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13c8eadf500000
start commit: 7f376f19 Merge tag 'mtd/fixes-for-5.10-rc8' of git://git.k..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=1028eadf500000
console output: https://syzkaller.appspot.com/x/log.txt?x=17c8eadf500000
kernel config: https://syzkaller.appspot.com/x/.config?x=3416bb960d5c705d
dashboard link: https://syzkaller.appspot.com/bug?extid=8971da381fb5a31f542d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128c5745500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a1f123500000
Reported-by: syzbot+8971da381fb5a31f542d@syzkaller.appspotmail.com
Fixes: b5b73b26b3ca ("taprio: Fix allowing too small intervals")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-12-15 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 9:44 general protection fault in taprio_dequeue_soft syzbot
2020-12-15 17:38 ` syzbot [this message]
2020-12-16 12:55 ` Davide Caratti
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=000000000000753add05b6843897@google.com \
--to=syzbot+8971da381fb5a31f542d@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vinicius.gomes@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 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).