From: syzbot <syzbot+3fbea977bd382a4e6140@syzkaller.appspotmail.com>
To: ast@kernel.org, bmt@zurich.ibm.com, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, dledford@redhat.com,
dsahern@gmail.com, hawk@kernel.org, jakub.kicinski@netronome.com,
jgg@ziepe.ca, jiri@mellanox.com, johannes.berg@intel.com,
john.fastabend@gmail.com, kafai@fb.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mkubecek@suse.cz, netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: Re: possible deadlock in siw_create_listen
Date: Sun, 08 Mar 2020 23:58:03 -0700 [thread overview]
Message-ID: <000000000000406a7f05a066861d@google.com> (raw)
In-Reply-To: <000000000000161ee805a039a49e@google.com>
syzbot has bisected this bug to:
commit bfcccfe78b361f5f6ef48554aed5bcd30c72f67f
Author: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue Nov 5 21:26:11 2019 +0000
netdevsim: drop code duplicated by a merge
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166d11c3e00000
start commit: 425c075d Merge branch 'tun-debug'
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=156d11c3e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=116d11c3e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=598678fc6e800071
dashboard link: https://syzkaller.appspot.com/bug?extid=3fbea977bd382a4e6140
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e3df31e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163d0439e00000
Reported-by: syzbot+3fbea977bd382a4e6140@syzkaller.appspotmail.com
Fixes: bfcccfe78b36 ("netdevsim: drop code duplicated by a merge")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-09 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 1:25 possible deadlock in siw_create_listen syzbot
2020-03-08 23:13 ` syzbot
2020-03-09 12:57 ` Jason Gunthorpe
2020-03-09 6:58 ` syzbot [this message]
2020-03-09 17:20 ` Jason Gunthorpe
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=000000000000406a7f05a066861d@google.com \
--to=syzbot+3fbea977bd382a4e6140@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=bmt@zurich.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=dsahern@gmail.com \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=jgg@ziepe.ca \
--cc=jiri@mellanox.com \
--cc=johannes.berg@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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).