Message-ID: <8b2e0e44-56d6-a585-6096-24d8ccc021f6@mellanox.com>
Date:   Tue, 9 Apr 2019 17:18:45 +0000
From:   Mark Bloch <markb@...lanox.com>
To:     Dmitry Vyukov <dvyukov@...gle.com>,
        syzbot <syzbot+6b46b135602a3f3ac99e@...kaller.appspotmail.com>
CC:     Daniel Jurgens <danielj@...lanox.com>,
        Doug Ledford <dledford@...hat.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Leon Romanovsky <leon@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        Parav Pandit <parav@...lanox.com>,
        "swise@...ngridcomputing.com" <swise@...ngridcomputing.com>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: general protection fault in rdma_listen (2)



On 4/9/19 6:57 AM, Dmitry Vyukov wrote:
> On Fri, Nov 16, 2018 at 6:44 PM syzbot
> <syzbot+6b46b135602a3f3ac99e@...kaller.appspotmail.com> wrote:
>>
>> syzbot has found a reproducer for the following crash on:
>>
>> HEAD commit:    da5322e65940 Merge tag 'selinux-pr-20181115' of git://git...
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=13a06f7b400000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
>> dashboard link: https://syzkaller.appspot.com/bug?extid=6b46b135602a3f3ac99e
>> compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10fa8a47400000
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+6b46b135602a3f3ac99e@...kaller.appspotmail.com
>>
>> IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
>> IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
>> 8021q: adding VLAN 0 to HW filter on device team0
>> kasan: CONFIG_KASAN_INLINE enabled
>> kasan: GPF could be caused by NULL-ptr deref or user memory access
>> general protection fault: 0000 [#1] PREEMPT SMP KASAN
>> CPU: 1 PID: 6328 Comm: syz-executor0 Not tainted 4.20.0-rc2+ #337
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
>> RIP: 0010:cma_bind_listen drivers/infiniband/core/cma.c:3355 [inline]
>> RIP: 0010:rdma_listen+0x357/0x990 drivers/infiniband/core/cma.c:3469
>> Code: 4c 8b ab c8 01 00 00 31 f6 48 c7 c7 60 3b db 89 e8 9e eb 25 02 48 b8
>> 00 00 00 00 00 fc ff df 49 8d 7d 08 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f
>> 85 64 05 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b
>> RSP: 0018:ffff8881b266f970 EFLAGS: 00010202
>> RAX: dffffc0000000000 RBX: ffff8881ba9a6d80 RCX: 0000000000000000
>> RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000008
>> RBP: ffff8881b266fa10 R08: fffffbfff13b6775 R09: fffffbfff13b6774
>> R10: ffff8881b266f960 R11: ffffffff89db3ba3 R12: 1ffff110364cdf31
>> R13: 0000000000000000 R14: 0000000000000003 R15: ffff8881d908fa80
>> FS:  00007f22f9e27700(0000) GS:ffff8881daf00000(0000) knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 00000000004cef08 CR3: 00000001ba4b4000 CR4: 00000000001406e0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>> Call Trace:
>>   ucma_listen+0x1a4/0x260 drivers/infiniband/core/ucma.c:1100
>>   ucma_write+0x365/0x460 drivers/infiniband/core/ucma.c:1689
>>   __vfs_write+0x119/0x9f0 fs/read_write.c:485
>>   vfs_write+0x1fc/0x560 fs/read_write.c:549
>>   ksys_write+0x101/0x260 fs/read_write.c:598
>>   __do_sys_write fs/read_write.c:610 [inline]
>>   __se_sys_write fs/read_write.c:607 [inline]
>>   __x64_sys_write+0x73/0xb0 fs/read_write.c:607
>>   do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
>>   entry_SYSCALL_64_after_hwframe+0x49/0xbe
>> RIP: 0033:0x457569
>> Code: fd b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
>> 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
>> ff 0f 83 cb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
>> RSP: 002b:00007f22f9e26c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
>> RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457569
>> RDX: 0000000000000010 RSI: 00000000200000c0 RDI: 0000000000000005
>> RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
>> R10: 0000000000000000 R11: 0000000000000246 R12: 00007f22f9e276d4
>> R13: 00000000004c571f R14: 00000000004d9360 R15: 00000000ffffffff
>> Modules linked in:
>> ---[ end trace ad276a0bcb316fb3 ]---
>> RIP: 0010:cma_bind_listen drivers/infiniband/core/cma.c:3355 [inline]
>> RIP: 0010:rdma_listen+0x357/0x990 drivers/infiniband/core/cma.c:3469
>> Code: 4c 8b ab c8 01 00 00 31 f6 48 c7 c7 60 3b db 89 e8 9e eb 25 02 48 b8
>> 00 00 00 00 00 fc ff df 49 8d 7d 08 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f
>> 85 64 05 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b
>> RSP: 0018:ffff8881b266f970 EFLAGS: 00010202
>> RAX: dffffc0000000000 RBX: ffff8881ba9a6d80 RCX: 0000000000000000
>> RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000008
>> RBP: ffff8881b266fa10 R08: fffffbfff13b6775 R09: fffffbfff13b6774
>> R10: ffff8881b266f960 R11: ffffffff89db3ba3 R12: 1ffff110364cdf31
>> R13: 0000000000000000 R14: 0000000000000003 R15: ffff8881d908fa80
>> FS:  00007f22f9e27700(0000) GS:ffff8881daf00000(0000) knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: ffffffffff600400 CR3: 00000001ba4b4000 CR4: 00000000001406e0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> 
> Hi Mark,
> 
> You tested some fixed for this bug. The latest tested patch did not
> trigger crash. Bug syzbot never seen any fixes for this bug. If you
> submitted the patch, please mark this bug as fixed.

Hi Dmitry,

I've talked with Jason (off list) at the time, and we agreed that while the patch
fixes the issue, it's just a band-aid that doesn't fix the underline issues with that code.

I think Parav has/had plans for a more comprehensive fix for that entire ucma.c code.

> 
> Thanks
> 

Thanks

Powered by blists - more mailing lists