Re: possible deadlock in _destroy_id

2020-11-25 Thread Jason Gunthorpe
On Wed, Nov 25, 2020 at 08:48:32AM +0200, Leon Romanovsky wrote: > > commit c80a0c52d85c49a910d0dc0e342e8d8898677dc0 > > Author: Leon Romanovsky > > Date: Wed Nov 4 16:40:07 2020 +0200 > > > > RDMA/cma: Add missing error handling of listen_id > > > > Don't silently continue if rdma_liste

Re: possible deadlock in _destroy_id

2020-11-24 Thread Leon Romanovsky
On Wed, Nov 18, 2020 at 09:37:56AM -0400, Jason Gunthorpe wrote: > On Wed, Nov 18, 2020 at 03:10:21AM -0800, syzbot wrote: > > > HEAD commit:20529233 Add linux-next specific files for 20201118 > > git tree: linux-next > > console output: https://syzkaller.appspot.com/x/log.txt?x=13093cf25

Re: possible deadlock in _destroy_id

2020-11-18 Thread syzbot
syzbot has found a reproducer for 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=16ce97be50 kernel config: https://syzkaller.appspot.com/x/.config?x=2c4fb58b6526b3

Re: possible deadlock in _destroy_id

2020-11-18 Thread Jason Gunthorpe
On Wed, Nov 18, 2020 at 03:10:21AM -0800, syzbot wrote: > HEAD commit:20529233 Add linux-next specific files for 20201118 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=13093cf250 > kernel config: https://syzkaller.appspot.com/x/.config?x=2c4fb58b

possible deadlock in _destroy_id

2020-11-18 Thread syzbot
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=13093cf250 kernel config: https://syzkaller.appspot.com/x/.config?x=2c4fb58b6526b3c1 dashboard