Date:   Thu, 08 Mar 2018 06:10:30 -0800
From:   syzbot <syzbot+6e81476d2dff22e77c18@...kaller.appspotmail.com>
To:     dasaratharaman.chandramouli@...el.com, dledford@...hat.com,
        jgg@...pe.ca, leonro@...lanox.com, linux-kernel@...r.kernel.org,
        linux-rdma@...r.kernel.org, markb@...lanox.com, monis@...lanox.com,
        parav@...lanox.com, syzkaller-bugs@...glegroups.com
Subject: general protection fault in rdma_listen

Hello,

syzbot hit the following crash on upstream commit
851710a8096131129ad1da79a47d385c4926d114 (Thu Mar 8 01:37:32 2018 +0000)
Merge branch 'for-linus' of  
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

So far this crash happened 7 times on upstream.
C reproducer is attached.
syzkaller reproducer is attached.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+6e81476d2dff22e77c18@...kaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for  
details.
If you forward the report, please keep this part and the footer.

IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
IPVS: ftp: loaded support on port[0] = 21
Dumping ftrace buffer:
    (ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 4307 Comm: syzkaller595147 Not tainted 4.16.0-rc4+ #345
IPVS: ftp: loaded support on port[0] = 21
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:rdma_listen+0x72/0x8e0 drivers/infiniband/core/cma.c:3300
RSP: 0018:ffff8801b60bf998 EFLAGS: 00010207
RAX: 0000000000000042 RBX: 0000000000000000 RCX: ffffffff841d7a24
RDX: 0000000000000000 RSI: 0000000000000400 RDI: 0000000000000214
RBP: ffff8801b60bfa30 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff88613380 R11: 0000000000000000 R12: 1ffff10036c17f35
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000400
FS:  00007f29d24eb700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f29d24c9e78 CR3: 00000001b0558006 CR4: 00000000001606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  ucma_listen+0x172/0x1f0 drivers/infiniband/core/ucma.c:1064
  ucma_write+0x2d6/0x3d0 drivers/infiniband/core/ucma.c:1627
  __vfs_write+0xef/0x970 fs/read_write.c:480
  vfs_write+0x189/0x510 fs/read_write.c:544
  SYSC_write fs/read_write.c:589 [inline]
  SyS_write+0xef/0x220 fs/read_write.c:581
  do_syscall_64+0x281/0x940 arch/x86/entry/common.c:287
  entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x449b59
RSP: 002b:00007f29d24eada8 EFLAGS: 00000297 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000006dbc5c RCX: 0000000000449b59
RDX: 0000000000000010 RSI: 0000000020004400 RDI: 000000000000000c
RBP: 00000000006dbc58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000297 R12: 006d635f616d6472
R13: 2f646e6162696e69 R14: 666e692f7665642f R15: 0000000000000006
Code: c0 79 1d 84 c7 00 f1 f1 f1 f1 c7 40 04 00 f2 f2 f2 c7 40 08 f3 f3 f3  
f3 e8 ec 8b 53 fd 48 8d bb 14 02 00 00 48 89 f8 48 c1 e8 03 <42> 0f b6 14  
28 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f
RIP: rdma_listen+0x72/0x8e0 drivers/infiniband/core/cma.c:3300 RSP:  
ffff8801b60bf998
---[ end trace 387a11ed6fffdaf9 ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
    (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is  
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug  
report.
Note: all commands must start from beginning of the line in the email body.

View attachment "raw.log.txt" of type "text/plain" (6872 bytes)

View attachment "repro.syz.txt" of type "text/plain" (743 bytes)

View attachment "repro.c.txt" of type "text/plain" (6126 bytes)

View attachment "config.txt" of type "text/plain" (137392 bytes)

Powered by blists - more mailing lists