[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201120183242.GR244516@ziepe.ca>
Date: Fri, 20 Nov 2020 14:32:42 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: syzbot <syzbot+76c931ae5fdee51fff5b@...kaller.appspotmail.com>
Cc: dledford@...hat.com, leon@...nel.org, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, parav@...lanox.com,
syzkaller-bugs@...glegroups.com
Subject: Re: possible deadlock in rdma_destroy_id
On Fri, Nov 20, 2020 at 07:15:21AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 20529233 Add linux-next specific files for 20201118
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=124ae36e500000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2c4fb58b6526b3c1
> dashboard link: https://syzkaller.appspot.com/bug?extid=76c931ae5fdee51fff5b
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+76c931ae5fdee51fff5b@...kaller.appspotmail.com
#syz dup: possible deadlock in _destroy_id
Powered by blists - more mailing lists