[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <001a113ee2f2f1403c0567010fff@google.com>
Date: Fri, 09 Mar 2018 12:59:03 -0800
From: syzbot <syzbot+7bed8439de3bce19a53e@...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_accept
Hello,
syzbot hit the following crash on upstream commit
1b88accf6a659c46d5c8e68912896f112bf882bb (Thu Mar 8 01:49:33 2018 +0000)
Merge tag 'for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost
So far this crash happened 2 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+7bed8439de3bce19a53e@...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.
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 4256 Comm: syzkaller154615 Not tainted 4.16.0-rc4+ #346
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:ucma_copy_conn_param drivers/infiniband/core/ucma.c:1021 [inline]
RIP: 0010:ucma_accept+0x4eb/0x970 drivers/infiniband/core/ucma.c:1085
RSP: 0018:ffff8801b9a4f8c8 EFLAGS: 00010202
RAX: ffff8801af1ec400 RBX: ffff8801b9a4f948 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000020
RBP: ffff8801b9a4fad0 R08: 0000000000000000 R09: 1ffff10037349f23
R10: ffffffff88613380 R11: 0000000000000000 R12: ffff8801b9a4f908
R13: ffff8801b9a4faa8 R14: ffff8801aeba3a00 R15: ffff8801afa34c00
FS: 00007f8d6f239700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8d6f238e78 CR3: 00000001b0505006 CR4: 00000000001606e0
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:0x445ae9
RSP: 002b:00007f8d6f238da8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000006dac3c RCX: 0000000000445ae9
RDX: 0000000000000128 RSI: 0000000020000780 RDI: 0000000000000003
RBP: 00000000006dac38 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 006d635f616d6472
R13: 2f646e6162696e69 R14: 666e692f7665642f R15: 0000000000000004
Code: 0c 09 84 c9 74 09 80 f9 03 0f 8e 4a 02 00 00 49 8d 78 20 41 89 b5 70
fe ff ff 48 b9 00 00 00 00 00 fc ff df 48 89 fe 48 c1 ee 03 <0f> b6 34 0e
48 89 f9 83 e1 07 83 c1 01 40 38 f1 7c 09 40 84 f6
RIP: ucma_copy_conn_param drivers/infiniband/core/ucma.c:1021 [inline] RSP:
ffff8801b9a4f8c8
RIP: ucma_accept+0x4eb/0x970 drivers/infiniband/core/ucma.c:1085 RSP:
ffff8801b9a4f8c8
---[ end trace efb43dccceaff67b ]---
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" (11539 bytes)
View attachment "repro.syz.txt" of type "text/plain" (1154 bytes)
View attachment "repro.c.txt" of type "text/plain" (5054 bytes)
View attachment "config.txt" of type "text/plain" (137392 bytes)
Powered by blists - more mailing lists