From: Leon Romanovsky <leon@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
syzbot <syzbot+2e3e485d5697ea610460@syzkaller.appspotmail.com>,
Matthew Wilcox <willy@infradead.org>,
danielj@mellanox.com, danitg@mellanox.com, dledford@redhat.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
parav@mellanox.com, swise@opengridcomputing.com,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in cma_exit_net
Date: Wed, 3 Apr 2019 08:11:40 +0300 [thread overview]
Message-ID: <20190403051140.GU3201@mtr-leonro.mtl.com> (raw)
In-Reply-To: <1554248352.118779.171.camel@acm.org>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
On Tue, Apr 02, 2019 at 04:39:12PM -0700, Bart Van Assche wrote:
> On Mon, 2019-04-01 at 21:29 +0300, Leon Romanovsky wrote:
> > On Mon, Apr 01, 2019 at 02:45:54PM -0300, Jason Gunthorpe wrote:
> > > On Mon, Apr 01, 2019 at 10:36:05AM -0700, syzbot wrote:
> > > > Hello,
> > > >
> > > > syzbot found the following crash on:
> > > >
> > > > HEAD commit: e3ecb83e Add linux-next specific files for 20190401
> > > > git tree: linux-next
> > > > console output: https://syzkaller.appspot.com/x/log.txt?x=13bc36cd200000
> > > > kernel config: https://syzkaller.appspot.com/x/.config?x=db6c9f2bfeb91a99
> > > > dashboard link: https://syzkaller.appspot.com/bug?extid=2e3e485d5697ea610460
> > > > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > > >
> > > > Unfortunately, I don't have any reproducer for this crash yet.
> > > >
> > > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > > Reported-by: syzbot+2e3e485d5697ea610460@syzkaller.appspotmail.com
> > > >
> > > > WARNING: CPU: 1 PID: 7 at drivers/infiniband/core/cma.c:4674
> > > > cma_exit_net+0x327/0x390 drivers/infiniband/core/cma.c:4674
> > > > Kernel panic - not syncing: panic_on_warn set ...
> > >
> > > Matt: This is why the WARN_ON(!xa_empty()) is so valuable. Magically
> > > syzkaller can find something in this code is buggy.
> > >
> > > Mellanox is also showing a different testing failure over the weekend
> > > (use after free or something) from your 'cma: Convert portspace IDRs
> > > to XArray'
> >
> > This is what I see in my environment.
Bart,
This patch [1] will fix it.
Thanks
[1] https://patchwork.kernel.org/patch/10881501/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2019-04-03 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 17:36 syzbot
2019-04-01 17:45 ` Jason Gunthorpe
2019-04-01 18:29 ` Leon Romanovsky
2019-04-02 23:39 ` Bart Van Assche
2019-04-03 5:11 ` Leon Romanovsky [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=20190403051140.GU3201@mtr-leonro.mtl.com \
--to=leon@kernel.org \
--cc=bvanassche@acm.org \
--cc=danielj@mellanox.com \
--cc=danitg@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=swise@opengridcomputing.com \
--cc=syzbot+2e3e485d5697ea610460@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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
Powered by JetHome