From: syzbot <syzbot+ec9b5cce58002d184fb6@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org,
leandro.maciel.dorileo@intel.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, vedang.patel@intel.com,
vinicius.gomes@intel.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] WARNING: ODEBUG bug in advance_sched
Date: Thu, 21 Dec 2023 11:33:07 -0800 [thread overview]
Message-ID: <000000000000450dee060d0a2bc3@google.com> (raw)
In-Reply-To: <000000000000f3d57d060d0556a1@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=116aaa79e80000
start commit: 1a44b0073b92 Merge tag 'ovl-fixes-6.7-rc7' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=136aaa79e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=156aaa79e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=314e9ad033a7d3a7
dashboard link: https://syzkaller.appspot.com/bug?extid=ec9b5cce58002d184fb6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d5bc6ee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1465cbd6e80000
Reported-by: syzbot+ec9b5cce58002d184fb6@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:[~2023-12-21 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:47 [syzbot] [net?] WARNING: ODEBUG bug in advance_sched syzbot
2023-12-21 19:33 ` syzbot [this message]
2024-11-11 19:31 ` syzbot
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=000000000000450dee060d0a2bc3@google.com \
--to=syzbot+ec9b5cce58002d184fb6@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vedang.patel@intel.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).