From: syzbot <syzbot+63bdb6006961d8c917c6@syzkaller.appspotmail.com>
To: davem@davemloft.net, echaudro@redhat.com, ivecera@redhat.com,
jhs@mojatatu.com, jiri@mellanox.com, jiri@resnulli.us,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com
Subject: Re: WARNING in cbq_destroy
Date: Wed, 22 Jan 2020 04:01:02 -0800 [thread overview]
Message-ID: <0000000000004762b3059cb947b4@google.com> (raw)
In-Reply-To: <0000000000007c3ba2059cb50843@google.com>
syzbot has bisected this bug to:
commit d51aae68b142f48232257e96ce317db25445418d
Author: Jiri Pirko <jiri@mellanox.com>
Date: Mon Nov 27 17:37:21 2017 +0000
net: sched: cbq: create block for q->link.block
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a51a95e00000
start commit: d96d875e Merge tag 'fixes_for_v5.5-rc8' of git://git.kerne..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=16a51a95e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=12a51a95e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=83c00afca9cf5153
dashboard link: https://syzkaller.appspot.com/bug?extid=63bdb6006961d8c917c6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a1a721e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11a91a95e00000
Reported-by: syzbot+63bdb6006961d8c917c6@syzkaller.appspotmail.com
Fixes: d51aae68b142 ("net: sched: cbq: create block for q->link.block")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-22 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 6:57 WARNING in cbq_destroy syzbot
2020-01-22 12:01 ` syzbot [this message]
2020-01-23 18:14 ` Cong Wang
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=0000000000004762b3059cb947b4@google.com \
--to=syzbot+63bdb6006961d8c917c6@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=echaudro@redhat.com \
--cc=ivecera@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.