general protection fault in ucma_init_qp_attr
4 views
Skip to first unread message
syzbot
Mar 25, 2018, 8:01:05 PM3/25/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot hit the following crash on upstream commit
cb6416592bc2a8b731dabcec0d63cda270764fc6 (Sun Mar 25 17:45:10 2018 +0000)
Merge tag 'dmaengine-fix-4.16-rc7' of
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=e1f82ae3a10894c4ed04
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5410880120422400
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-5034017172441945317
compiler: gcc (GCC) 7.1.1 20170620
CC: [dasaratharama...@intel.com dled...@redhat.com j...@ziepe.ca
leo...@mellanox.com linux-...@vger.kernel.org linux...@vger.kernel.org
ma...@mellanox.com mo...@mellanox.com pa...@mellanox.com]
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e1f82a...@syzkaller.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: GPF could be caused by NULL-ptr deref or user memory access
entry_SYSCALL_64_after_hwframe+0x42/0xb7
general protection fault: 0000 [#1] SMP KASAN
RIP: 0033:0x454879
Dumping ftrace buffer:
RSP: 002b:00007f1c48d9dc68 EFLAGS: 00000246
(ftrace buffer empty)
ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007f1c48d9e6d4 RCX: 0000000000454879
Modules linked in:
RDX: 0000000000000040 RSI: 0000000000000029 RDI: 0000000000000015
RBP: 000000000072bea0 R08: 0000000000000004 R09: 0000000000000000
CPU: 0 PID: 21877 Comm: syz-executor1 Not tainted 4.16.0-rc6+ #366
R10: 0000000020001fde R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000052c R14: 00000000006f8cc0 R15: 0000000000000000
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Mem-Info:
RIP: 0010:rdma_cap_ib_cm include/rdma/ib_verbs.h:2661 [inline]
RIP: 0010:rdma_init_qp_attr+0x8b/0x720 drivers/infiniband/core/cma.c:1025
RSP: 0018:ffff8801933ff840 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff8801b2155b40 RCX: ffffffff841bc03f
active_anon:70404 inactive_anon:62 isolated_anon:0
active_file:3622 inactive_file:8113 isolated_file:0
unevictable:0 dirty:81 writeback:0 unstable:0
slab_reclaimable:11482 slab_unreclaimable:185825
mapped:24295 shmem:71 pagetables:699 bounce:0
free:1308731 free_pcp:327 free_cma:0
RDX: 0000000000000029 RSI: ffffc900029c5000 RDI: 0000000000000148
RBP: ffff8801933ff880 R08: ffffed003267ff4e R09: ffff8801933ff9cc
R10: 0000000000000000 R11: ffffed003267ff4d R12: ffff8801933ff9c8
R13: ffff8801933ff908 R14: 0000000000000000 R15: ffff8801933ff8c8
FS: 00007f8b74813700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
Node 0 active_anon:281616kB inactive_anon:248kB active_file:14488kB
inactive_file:32452kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
mapped:97180kB dirty:324kB writeback:0kB shmem:284kB shmem_thp: 0kB
shmem_pmdmapped: 0kB anon_thp: 45056kB writeback_tmp:0kB unstable:0kB
all_unreclaimable? no
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b9bc21000 CR3: 0000000192e77002 CR4: 00000000001606f0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Node 0
Call Trace:
ucma_init_qp_attr+0x251/0x440 drivers/infiniband/core/ucma.c:1172
DMA free:15908kB min:164kB low:204kB high:244kB active_anon:0kB
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB
writepending:0kB present:15992kB managed:15908kB mlocked:0kB
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB
free_cma:0kB
lowmem_reserve[]:
ucma_write+0x2d6/0x3d0 drivers/infiniband/core/ucma.c:1649
0
2864
__vfs_write+0xef/0x970 fs/read_write.c:480
6373
6373
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
Node 0
DMA32 free:2934564kB min:30292kB low:37864kB high:45436kB active_anon:0kB
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB
writepending:0kB present:3129292kB managed:2935312kB mlocked:0kB
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:748kB local_pcp:676kB
free_cma:0kB
do_syscall_64+0x281/0x940 arch/x86/entry/common.c:287
lowmem_reserve[]:
0
0
3509
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x454879
3509
RSP: 002b:00007f8b74812c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8b748136d4 RCX: 0000000000454879
RDX: 0000000000000018 RSI: 0000000020000cc0 RDI: 0000000000000013
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000683 R14: 00000000006face8 R15: 0000000000000000
Code:
Node 0
00 00 00 fc ff df
Normal free:2284452kB min:37120kB low:46400kB high:55680kB
active_anon:281616kB inactive_anon:248kB active_file:14488kB
inactive_file:32452kB unevictable:0kB writepending:324kB present:4718592kB
managed:3593744kB mlocked:0kB kernel_stack:5984kB pagetables:2796kB
bounce:0kB free_pcp:560kB local_pcp:276kB free_cma:0kB
80 3c 02 00 0f 85 8c
lowmem_reserve[]:
06 00 00 4c 8b 33 48
0
b8 00 00 00 00 00 fc
0
ff df 49 8d be 48 01
0
00 00 48 89 fa 48 c1 ea
0
03 <80> 3c 02 00 0f 85
5d 06 00 00 44 0f b6 7d
Node 0
d4 48 b8 00 00 00 00
DMA:
RIP: rdma_cap_ib_cm include/rdma/ib_verbs.h:2661 [inline] RSP:
ffff8801933ff840
RIP: rdma_init_qp_attr+0x8b/0x720 drivers/infiniband/core/cma.c:1025 RSP:
ffff8801933ff840
---[ end trace 1ec7cbce9dac73be ]---
1*4kB
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.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
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.
To upstream this report, please reply with:
#syz upstream
syzbot hit the following crash on upstream commit
cb6416592bc2a8b731dabcec0d63cda270764fc6 (Sun Mar 25 17:45:10 2018 +0000)
Merge tag 'dmaengine-fix-4.16-rc7' of
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=e1f82ae3a10894c4ed04
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5410880120422400
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-5034017172441945317
compiler: gcc (GCC) 7.1.1 20170620
CC: [dasaratharama...@intel.com dled...@redhat.com j...@ziepe.ca
leo...@mellanox.com linux-...@vger.kernel.org linux...@vger.kernel.org
ma...@mellanox.com mo...@mellanox.com pa...@mellanox.com]
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e1f82a...@syzkaller.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: GPF could be caused by NULL-ptr deref or user memory access
entry_SYSCALL_64_after_hwframe+0x42/0xb7
general protection fault: 0000 [#1] SMP KASAN
RIP: 0033:0x454879
Dumping ftrace buffer:
RSP: 002b:00007f1c48d9dc68 EFLAGS: 00000246
(ftrace buffer empty)
ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007f1c48d9e6d4 RCX: 0000000000454879
Modules linked in:
RDX: 0000000000000040 RSI: 0000000000000029 RDI: 0000000000000015
RBP: 000000000072bea0 R08: 0000000000000004 R09: 0000000000000000
CPU: 0 PID: 21877 Comm: syz-executor1 Not tainted 4.16.0-rc6+ #366
R10: 0000000020001fde R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000052c R14: 00000000006f8cc0 R15: 0000000000000000
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Mem-Info:
RIP: 0010:rdma_cap_ib_cm include/rdma/ib_verbs.h:2661 [inline]
RIP: 0010:rdma_init_qp_attr+0x8b/0x720 drivers/infiniband/core/cma.c:1025
RSP: 0018:ffff8801933ff840 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff8801b2155b40 RCX: ffffffff841bc03f
active_anon:70404 inactive_anon:62 isolated_anon:0
active_file:3622 inactive_file:8113 isolated_file:0
unevictable:0 dirty:81 writeback:0 unstable:0
slab_reclaimable:11482 slab_unreclaimable:185825
mapped:24295 shmem:71 pagetables:699 bounce:0
free:1308731 free_pcp:327 free_cma:0
RDX: 0000000000000029 RSI: ffffc900029c5000 RDI: 0000000000000148
RBP: ffff8801933ff880 R08: ffffed003267ff4e R09: ffff8801933ff9cc
R10: 0000000000000000 R11: ffffed003267ff4d R12: ffff8801933ff9c8
R13: ffff8801933ff908 R14: 0000000000000000 R15: ffff8801933ff8c8
FS: 00007f8b74813700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
Node 0 active_anon:281616kB inactive_anon:248kB active_file:14488kB
inactive_file:32452kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
mapped:97180kB dirty:324kB writeback:0kB shmem:284kB shmem_thp: 0kB
shmem_pmdmapped: 0kB anon_thp: 45056kB writeback_tmp:0kB unstable:0kB
all_unreclaimable? no
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b9bc21000 CR3: 0000000192e77002 CR4: 00000000001606f0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Node 0
Call Trace:
ucma_init_qp_attr+0x251/0x440 drivers/infiniband/core/ucma.c:1172
DMA free:15908kB min:164kB low:204kB high:244kB active_anon:0kB
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB
writepending:0kB present:15992kB managed:15908kB mlocked:0kB
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB
free_cma:0kB
lowmem_reserve[]:
ucma_write+0x2d6/0x3d0 drivers/infiniband/core/ucma.c:1649
0
2864
__vfs_write+0xef/0x970 fs/read_write.c:480
6373
6373
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
Node 0
DMA32 free:2934564kB min:30292kB low:37864kB high:45436kB active_anon:0kB
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB
writepending:0kB present:3129292kB managed:2935312kB mlocked:0kB
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:748kB local_pcp:676kB
free_cma:0kB
do_syscall_64+0x281/0x940 arch/x86/entry/common.c:287
lowmem_reserve[]:
0
0
3509
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x454879
3509
RSP: 002b:00007f8b74812c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8b748136d4 RCX: 0000000000454879
RDX: 0000000000000018 RSI: 0000000020000cc0 RDI: 0000000000000013
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000683 R14: 00000000006face8 R15: 0000000000000000
Code:
Node 0
00 00 00 fc ff df
Normal free:2284452kB min:37120kB low:46400kB high:55680kB
active_anon:281616kB inactive_anon:248kB active_file:14488kB
inactive_file:32452kB unevictable:0kB writepending:324kB present:4718592kB
managed:3593744kB mlocked:0kB kernel_stack:5984kB pagetables:2796kB
bounce:0kB free_pcp:560kB local_pcp:276kB free_cma:0kB
80 3c 02 00 0f 85 8c
lowmem_reserve[]:
06 00 00 4c 8b 33 48
0
b8 00 00 00 00 00 fc
0
ff df 49 8d be 48 01
0
00 00 48 89 fa 48 c1 ea
0
03 <80> 3c 02 00 0f 85
5d 06 00 00 44 0f b6 7d
Node 0
d4 48 b8 00 00 00 00
DMA:
RIP: rdma_cap_ib_cm include/rdma/ib_verbs.h:2661 [inline] RSP:
ffff8801933ff840
RIP: rdma_init_qp_attr+0x8b/0x720 drivers/infiniband/core/cma.c:1025 RSP:
ffff8801933ff840
---[ end trace 1ec7cbce9dac73be ]---
1*4kB
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.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
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.
To upstream this report, please reply with:
#syz upstream
syzbot
Feb 22, 2019, 5:34:45 AM2/22/19
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages