From: syzbot <syzbot+4b628fcc748474003457@syzkaller.appspotmail.com>
To: dledford@redhat.com, haggaie@mellanox.com,
hal.rosenstock@gmail.com, jgg@ziepe.ca, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
parav@mellanox.com, raindel@mellanox.com, roland@purestorage.com,
sean.hefty@intel.com, swise@opengridcomputing.com,
syzkaller-bugs@googlegroups.com, yishaih@mellanox.com
Subject: Re: WARNING: bad unlock balance in ucma_destroy_id
Date: Wed, 10 Apr 2019 23:53:01 -0700 [thread overview]
Message-ID: <000000000000192b4405863ba337@google.com> (raw)
In-Reply-To: <0000000000003b9c4b0574806070@google.com>
syzbot has bisected this bug to:
commit e1c30298ccab87151a0c4241fc5985c591598361
Author: Yishai Hadas <yishaih@mellanox.com>
Date: Thu Aug 13 15:32:07 2015 +0000
IB/ucma: HW Device hot-removal support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=157538d3200000
start commit: 5b394b2d Linux 4.19-rc1
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=177538d3200000
console output: https://syzkaller.appspot.com/x/log.txt?x=137538d3200000
kernel config: https://syzkaller.appspot.com/x/.config?x=49927b422dcf0b29
dashboard link: https://syzkaller.appspot.com/bug?extid=4b628fcc748474003457
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13351e2e400000
Reported-by: syzbot+4b628fcc748474003457@syzkaller.appspotmail.com
Fixes: e1c30298ccab ("IB/ucma: HW Device hot-removal support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-04-11 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 15:20 WARNING: bad unlock balance in ucma_destroy_id syzbot
2019-04-11 6:53 ` 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=000000000000192b4405863ba337@google.com \
--to=syzbot+4b628fcc748474003457@syzkaller.appspotmail.com \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=hal.rosenstock@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=raindel@mellanox.com \
--cc=roland@purestorage.com \
--cc=sean.hefty@intel.com \
--cc=swise@opengridcomputing.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yishaih@mellanox.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