From: syzbot <syzbot+3b165dac15094065651e@syzkaller.appspotmail.com>
To: ap420073@gmail.com, 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,
xiyou.wangcong@gmail.com
Subject: Re: possible deadlock in __dev_queue_xmit (3)
Date: Sun, 02 Aug 2020 00:43:05 -0700 [thread overview]
Message-ID: <0000000000002fa64705abe02c21@google.com> (raw)
In-Reply-To: <000000000000ea90600598c9b089@google.com>
syzbot has bisected this issue to:
commit 1a33e10e4a95cb109ff1145098175df3113313ef
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Sun May 3 05:22:19 2020 +0000
net: partially revert dynamic lockdep key changes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10434970900000
start commit: d8b9faec Merge tag 'drm-fixes-2020-07-31' of git://anongit..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12434970900000
console output: https://syzkaller.appspot.com/x/log.txt?x=14434970900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0cfcf935bcc94d2
dashboard link: https://syzkaller.appspot.com/bug?extid=3b165dac15094065651e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163e2c92900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=143f2bb8900000
Reported-by: syzbot+3b165dac15094065651e@syzkaller.appspotmail.com
Fixes: 1a33e10e4a95 ("net: partially revert dynamic lockdep key changes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-02 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 9:55 possible deadlock in __dev_queue_xmit (3) syzbot
2020-07-31 7:12 ` syzbot
2020-08-02 7:43 ` 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=0000000000002fa64705abe02c21@google.com \
--to=syzbot+3b165dac15094065651e@syzkaller.appspotmail.com \
--cc=ap420073@gmail.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=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.