From: syzbot <syzbot+08e3d39f3eb8643216be@syzkaller.appspotmail.com>
To: ap420073@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: Re: possible deadlock in dev_mc_unsync
Date: Tue, 11 Aug 2020 05:07:04 -0700 [thread overview]
Message-ID: <000000000000d683c505ac98e87e@google.com> (raw)
In-Reply-To: <000000000000cf1be105a8ffc44c@google.com>
syzbot suspects this issue was fixed by commit:
commit be74294ffa24f5fbc0d6643842e3e095447e17a2
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Fri Jun 26 18:24:22 2020 +0000
net: get rid of lockdep_set_class_and_subclass()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=110b0fc2900000
start commit: 4a21185c Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=bf3aec367b9ab569
dashboard link: https://syzkaller.appspot.com/bug?extid=08e3d39f3eb8643216be
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d2b1c5100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17aed775100000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: get rid of lockdep_set_class_and_subclass()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-11 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 17:09 possible deadlock in dev_mc_unsync syzbot
2020-06-27 13:19 ` syzbot
2020-06-27 18:07 ` Cong Wang
2020-06-28 14:11 ` syzbot
2020-08-11 12:07 ` syzbot [this message]
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=000000000000d683c505ac98e87e@google.com \
--to=syzbot+08e3d39f3eb8643216be@syzkaller.appspotmail.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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 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).