From: syzbot <syzbot+e67cf584b5e6b35a8ffa@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, aviadye@mellanox.com, borisp@mellanox.com,
daniel@iogearbox.net, davejwatson@fb.com, davem@davemloft.net,
jakub.kicinski@netronome.com, john.fastabend@gmail.com,
john.hurley@netronome.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, simon.horman@netronome.com,
syzkaller-bugs@googlegroups.com, willemb@google.com,
xiyou.wangcong@gmail.com
Subject: Re: BUG: spinlock recursion in release_sock
Date: Wed, 24 Jul 2019 16:14:00 -0700 [thread overview]
Message-ID: <000000000000e8c654058e7576ef@google.com> (raw)
In-Reply-To: <000000000000464b54058e722b54@google.com>
syzbot has bisected this bug to:
commit 8822e270d697010e6a4fd42a319dbefc33db91e1
Author: John Hurley <john.hurley@netronome.com>
Date: Sun Jul 7 14:01:54 2019 +0000
net: core: move push MPLS functionality from OvS to core helper
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ca5a5c600000
start commit: 9e6dfe80 Add linux-next specific files for 20190724
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=102a5a5c600000
console output: https://syzkaller.appspot.com/x/log.txt?x=17ca5a5c600000
kernel config: https://syzkaller.appspot.com/x/.config?x=6cbb8fc2cf2842d7
dashboard link: https://syzkaller.appspot.com/bug?extid=e67cf584b5e6b35a8ffa
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13680594600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b34144600000
Reported-by: syzbot+e67cf584b5e6b35a8ffa@syzkaller.appspotmail.com
Fixes: 8822e270d697 ("net: core: move push MPLS functionality from OvS to
core helper")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-07-24 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 19:18 BUG: spinlock recursion in release_sock syzbot
2019-07-24 23:14 ` syzbot [this message]
2019-07-25 14:32 ` John Fastabend
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=000000000000e8c654058e7576ef@google.com \
--to=syzbot+e67cf584b5e6b35a8ffa@syzkaller.appspotmail.com \
--cc=arvid.brodin@alten.se \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=john.hurley@netronome.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willemb@google.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