Date:   Sun, 11 Mar 2018 10:59:01 -0700
From:   syzbot <syzbot+b112de930fe45b40da14@...kaller.appspotmail.com>
To:     dasaratharaman.chandramouli@...el.com, dledford@...hat.com,
        don.hiatt@...el.com, jgg@...pe.ca, leon@...nel.org,
        linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
        parav@...lanox.com, syzkaller-bugs@...glegroups.com,
        viro@...iv.linux.org.uk
Subject: general protection fault in ucma_query_route

Hello,

syzbot hit the following crash on upstream commit
cdb06e9d8f520c969676e7d6778cffe5894f079f (Sat Mar 10 00:59:19 2018 +0000)
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm

So far this crash happened 3 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+b112de930fe45b40da14@...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.

audit: type=1400 audit(1520695981.323:7): avc:  denied  { map } for   
pid=4243 comm="syzkaller725999" path="/root/syzkaller725999096" dev="sda1"  
ino=16481 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023  
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
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
Dumping ftrace buffer:
    (ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 4245 Comm: syzkaller725999 Not tainted 4.16.0-rc4+ #348
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:ucma_query_route+0x15e/0x1080 drivers/infiniband/core/ucma.c:817
RSP: 0018:ffff8801af29f910 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 1ffff10035e53f26 RCX: 0000000000000000
RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffff8801cb070bb0
RBP: ffff8801af29fac0 R08: ffffed0035e53f4b R09: ffff8801af29f990
R10: 0000000000000000 R11: ffffed0035e53f4a R12: ffff8801cb070b40
R13: ffff8801af29f990 R14: 0000000000000020 R15: 0000000000000000
FS:  00007fb3e61b1700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb3e618fe78 CR3: 00000001af5a9005 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  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:0x4457a9
RSP: 002b:00007fb3e61b0da8 EFLAGS: 00000297 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000006dac5c RCX: 00000000004457a9
RDX: 0000000000000018 RSI: 00000000200027c0 RDI: 000000000000000d
RBP: 00000000006dac58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000297 R12: 006d635f616d6472
R13: 2f646e6162696e69 R14: 666e692f7665642f R15: 0000000000000006
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bb 0c 00 00 4d 8b 7c 24 70 48  
b8 00 00 00 00 00 fc ff df 4d 8d 77 20 4c 89 f2 48 c1 ea 03 <0f> b6 14 02  
4c 89 f0 83 e0 07 83 c0 01 38 d0 7c 08 84 d2 0f 85
RIP: ucma_query_route+0x15e/0x1080 drivers/infiniband/core/ucma.c:817 RSP:  
ffff8801af29f910
---[ end trace 72b57b773bd012e1 ]---
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" (5623 bytes)

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

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

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

Powered by blists - more mailing lists