From: syzbot <syzbot+80e32b5d1f9923f8ace6@syzkaller.appspotmail.com>
To: davem@davemloft.net, eric.dumazet@gmail.com, jhs@mojatatu.com,
jiri@mellanox.com, jiri@resnulli.us, kuba@kernel.org,
linux-kernel@vger.kernel.org, marcelo.leitner@gmail.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
vladbu@mellanox.com, xiyou.wangcong@gmail.com
Subject: Re: INFO: task hung in tcf_ife_init
Date: Thu, 03 Sep 2020 08:33:06 -0700 [thread overview]
Message-ID: <000000000000fcd01005ae6a77e7@google.com> (raw)
In-Reply-To: <00000000000014fd1405ae64d01f@google.com>
syzbot has bisected this issue to:
commit 4e8ddd7f1758ca4ddd0c1f7cf3e66fce736241d2
Author: Vlad Buslov <vladbu@mellanox.com>
Date: Thu Jul 5 14:24:30 2018 +0000
net: sched: don't release reference on action overwrite
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14ae08e9900000
start commit: 1996cf46 net: bcmgenet: fix mask check in bcmgenet_validat..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=16ae08e9900000
console output: https://syzkaller.appspot.com/x/log.txt?x=12ae08e9900000
kernel config: https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=80e32b5d1f9923f8ace6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=161678e1900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f826d1900000
Reported-by: syzbot+80e32b5d1f9923f8ace6@syzkaller.appspotmail.com
Fixes: 4e8ddd7f1758 ("net: sched: don't release reference on action overwrite")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-03 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 8:48 INFO: task hung in tcf_ife_init syzbot
2020-09-03 9:47 ` Eric Dumazet
2020-09-03 18:11 ` Cong Wang
2020-09-03 15:33 ` syzbot [this message]
2020-09-03 17:08 ` Vlad Buslov
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=000000000000fcd01005ae6a77e7@google.com \
--to=syzbot+80e32b5d1f9923f8ace6@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vladbu@mellanox.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.