[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <94eb2c030cc438d6720566cd18dd@google.com>
Date: Tue, 06 Mar 2018 22:59:04 -0800
From: syzbot <syzbot+160331a9533b151c8651@...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_disconnect
Hello,
syzbot hit the following crash on upstream commit
ce380619fab99036f5e745c7a865b21c59f005f6 (Tue Mar 6 04:31:14 2018 +0000)
Merge tag 'please-pull-ia64_misc' of
git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux
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+160331a9533b151c8651@...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.
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: 4294 Comm: syzkaller511238 Not tainted 4.16.0-rc4+ #343
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:rdma_disconnect+0x2d/0x200 drivers/infiniband/core/cma.c:3878
RSP: 0018:ffff8801cee7fa10 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 1ffff10039dcff49 RCX: ffffffff841bc3fc
RDX: 0000000000000078 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8801cee7fa38 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff88613380 R11: 0000000000000000 R12: ffff8801af83a000
R13: 00000000000003c0 R14: 0000000000000000 R15: 00000000200001c8
FS: 00007f20217de700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f202179be78 CR3: 00000001dad71002 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ucma_disconnect+0xdf/0x150 drivers/infiniband/core/ucma.c:1131
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:0x4497c9
RSP: 002b:00007f20217ddda8 EFLAGS: 00000297 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000006dac5c RCX: 00000000004497c9
RDX: 000000000000000c RSI: 00000000200001c0 RDI: 0000000000000003
RBP: 00000000006dac58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000297 R12: 006d635f616d6472
R13: 2f646e6162696e69 R14: 666e692f7665642f R15: 0000000000000006
Code: 89 e5 41 57 41 56 49 89 fe 41 55 41 54 4d 8d ae c0 03 00 00 53 e8 34
42 55 fd 4c 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00
0f 85 b8 01 00 00 4d 8b a6 c0 03 00 00 4d 85 e4 0f
RIP: rdma_disconnect+0x2d/0x200 drivers/infiniband/core/cma.c:3878 RSP:
ffff8801cee7fa10
---[ end trace 4f57ea5e283fed6e ]---
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" (7465 bytes)
View attachment "repro.syz.txt" of type "text/plain" (700 bytes)
View attachment "repro.c.txt" of type "text/plain" (4214 bytes)
View attachment "config.txt" of type "text/plain" (137392 bytes)
Powered by blists - more mailing lists