INFO: task hung in install_new_memslots
7 views
Skip to first unread message
syzbot
Sep 9, 2018, 4:31:04 AM9/9/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: f2b6e66e9885 Add linux-next specific files for 20180904
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10b64e46400000
kernel config: https://syzkaller.appspot.com/x/.config?x=15ad48400e39c1b3
dashboard link: https://syzkaller.appspot.com/bug?extid=95553850e68a1f806f66
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [k...@vger.kernel.org linux-...@vger.kernel.org
pbon...@redhat.com rkr...@redhat.com]
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+955538...@syzkaller.appspotmail.com
dccp_v4_rcv: dropped packet with invalid checksum
dccp_v4_rcv: dropped packet with invalid checksum
INFO: task syz-executor4:8120 blocked for more than 140 seconds.
Not tainted 4.19.0-rc2-next-20180904+ #55
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor4 D23592 8120 4667 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x87c/0x1df0 kernel/sched/core.c:3473
schedule+0xfb/0x450 kernel/sched/core.c:3517
schedule_timeout+0x1cc/0x260 kernel/time/timer.c:1780
do_wait_for_common kernel/sched/completion.c:83 [inline]
__wait_for_common kernel/sched/completion.c:104 [inline]
wait_for_common kernel/sched/completion.c:115 [inline]
wait_for_completion+0x430/0x8d0 kernel/sched/completion.c:136
__synchronize_srcu+0x189/0x240 kernel/rcu/srcutree.c:934
synchronize_srcu_expedited+0x18/0x20 kernel/rcu/srcutree.c:959
install_new_memslots+0x20a/0x4b0
arch/x86/kvm/../../../virt/kvm/kvm_main.c:885
__kvm_set_memory_region+0x1be6/0x2e60
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1060
kvm_set_memory_region+0x2e/0x50
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1083
kvm_vm_ioctl_set_memory_region
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1095 [inline]
kvm_vm_ioctl+0x664/0x1d80 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2987
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x456f07
Code: 1c 00 00 00 e8 ea 49 fd ff 0f 0b e8 63 30 00 00 eb c1 cc 64 48 8b 0c
25 f8 ff ff ff 48 3b 61 10 0f 86 bd 02 00 00 48 83 ec 58 <48> 89 6c 24 50
48 8d 6c 24 50 48 8b 42 08 48 89 44 24 40 48 8b 4a
RSP: 002b:00007fde4782d098 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 0000000000456f07
RDX: 00007fde4782d510 RSI: 000000004020ae46 RDI: 0000000000000009
RBP: 000000002000d000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000fec00000
R13: 0000000000000009 R14: 00000000004c9fc0 R15: 0000000000000002
Showing all locks held in the system:
1 lock held by kworker/1:0/18:
1 lock held by khungtaskd/792:
#0: 00000000a82a00d1 (rcu_read_lock){....}, at:
debug_show_all_locks+0xd0/0x428 kernel/locking/lockdep.c:4436
2 locks held by rsyslogd/4525:
2 locks held by getty/4615:
#0: 0000000034812364 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000e16f5cfc (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4616:
#0: 00000000b017ef38 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000013f3689a (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4617:
#0: 000000007a055688 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000006fe9f012 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4618:
#0: 00000000bd07d28a (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000003f803720 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4619:
#0: 000000006902fd60 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000c68d6051 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4620:
#0: 000000003c929095 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000004bcd7a23 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4621:
#0: 00000000f09c5d87 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000868d38eb (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
1 lock held by syz-executor4/8120:
#0: 00000000f417f567 (&kvm->slots_lock){+.+.}, at:
kvm_set_memory_region+0x23/0x50
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1082
2 locks held by syz-executor4/8123:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 792 Comm: khungtaskd Not tainted 4.19.0-rc2-next-20180904+ #55
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x48/0x88 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x151/0x192 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:144 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
watchdog+0xb39/0x1040 kernel/hung_task.c:265
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 18 Comm: kworker/1:0 Not tainted 4.19.0-rc2-next-20180904+ #55
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: rcu_gp process_srcu
RIP: 0010:rdtsc arch/x86/include/asm/msr.h:205 [inline]
RIP: 0010:rdtsc_ordered arch/x86/include/asm/msr.h:232 [inline]
RIP: 0010:delay_tsc+0x26/0x70 arch/x86/lib/delay.c:61
Code: 1f 44 00 00 55 65 ff 05 58 d2 2d 79 48 89 e5 65 8b 35 ae 65 2d 79 0f
ae e8 0f 31 48 c1 e2 20 48 89 d1 48 09 c1 0f ae e8 0f 31 <48> c1 e2 20 48
09 d0 48 89 c2 48 29 ca 48 39 fa 73 25 65 ff 0d 21
RSP: 0018:ffff8801d9f5f140 EFLAGS: 00000246
RAX: 00000000f6a2b2c8 RBX: dffffc0000000000 RCX: 000000f3f6a296fc
RDX: 00000000000000f3 RSI: 0000000000000001 RDI: 0000000000002ced
RBP: ffff8801d9f5f140 R08: ffff8801d9f504c0 R09: 0000000000000005
R10: 1ffffd1ffffba200 R11: ffffc90001945b87 R12: 0000000000000001
R13: ffffc900019457e0 R14: ffffc900019457e0 R15: ffff8801d9f5f2c8
FS: 0000000000000000(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7119f1f140 CR3: 00000001bef14000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__delay arch/x86/lib/delay.c:161 [inline]
__const_udelay+0x61/0x80 arch/x86/lib/delay.c:175
try_check_zero+0x36f/0x5d0 kernel/rcu/srcutree.c:721
srcu_advance_state kernel/rcu/srcutree.c:1155 [inline]
process_srcu+0x6dc/0x14a0 kernel/rcu/srcutree.c:1249
process_one_work+0xc73/0x1aa0 kernel/workqueue.c:2153
worker_thread+0x189/0x13c0 kernel/workqueue.c:2296
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:415
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot found the following crash on:
HEAD commit: f2b6e66e9885 Add linux-next specific files for 20180904
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10b64e46400000
kernel config: https://syzkaller.appspot.com/x/.config?x=15ad48400e39c1b3
dashboard link: https://syzkaller.appspot.com/bug?extid=95553850e68a1f806f66
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [k...@vger.kernel.org linux-...@vger.kernel.org
pbon...@redhat.com rkr...@redhat.com]
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+955538...@syzkaller.appspotmail.com
dccp_v4_rcv: dropped packet with invalid checksum
dccp_v4_rcv: dropped packet with invalid checksum
INFO: task syz-executor4:8120 blocked for more than 140 seconds.
Not tainted 4.19.0-rc2-next-20180904+ #55
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor4 D23592 8120 4667 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x87c/0x1df0 kernel/sched/core.c:3473
schedule+0xfb/0x450 kernel/sched/core.c:3517
schedule_timeout+0x1cc/0x260 kernel/time/timer.c:1780
do_wait_for_common kernel/sched/completion.c:83 [inline]
__wait_for_common kernel/sched/completion.c:104 [inline]
wait_for_common kernel/sched/completion.c:115 [inline]
wait_for_completion+0x430/0x8d0 kernel/sched/completion.c:136
__synchronize_srcu+0x189/0x240 kernel/rcu/srcutree.c:934
synchronize_srcu_expedited+0x18/0x20 kernel/rcu/srcutree.c:959
install_new_memslots+0x20a/0x4b0
arch/x86/kvm/../../../virt/kvm/kvm_main.c:885
__kvm_set_memory_region+0x1be6/0x2e60
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1060
kvm_set_memory_region+0x2e/0x50
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1083
kvm_vm_ioctl_set_memory_region
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1095 [inline]
kvm_vm_ioctl+0x664/0x1d80 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2987
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x456f07
Code: 1c 00 00 00 e8 ea 49 fd ff 0f 0b e8 63 30 00 00 eb c1 cc 64 48 8b 0c
25 f8 ff ff ff 48 3b 61 10 0f 86 bd 02 00 00 48 83 ec 58 <48> 89 6c 24 50
48 8d 6c 24 50 48 8b 42 08 48 89 44 24 40 48 8b 4a
RSP: 002b:00007fde4782d098 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 0000000000456f07
RDX: 00007fde4782d510 RSI: 000000004020ae46 RDI: 0000000000000009
RBP: 000000002000d000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000fec00000
R13: 0000000000000009 R14: 00000000004c9fc0 R15: 0000000000000002
Showing all locks held in the system:
1 lock held by kworker/1:0/18:
1 lock held by khungtaskd/792:
#0: 00000000a82a00d1 (rcu_read_lock){....}, at:
debug_show_all_locks+0xd0/0x428 kernel/locking/lockdep.c:4436
2 locks held by rsyslogd/4525:
2 locks held by getty/4615:
#0: 0000000034812364 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000e16f5cfc (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4616:
#0: 00000000b017ef38 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000013f3689a (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4617:
#0: 000000007a055688 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000006fe9f012 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4618:
#0: 00000000bd07d28a (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000003f803720 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4619:
#0: 000000006902fd60 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000c68d6051 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4620:
#0: 000000003c929095 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000004bcd7a23 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4621:
#0: 00000000f09c5d87 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000868d38eb (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
1 lock held by syz-executor4/8120:
#0: 00000000f417f567 (&kvm->slots_lock){+.+.}, at:
kvm_set_memory_region+0x23/0x50
arch/x86/kvm/../../../virt/kvm/kvm_main.c:1082
2 locks held by syz-executor4/8123:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 792 Comm: khungtaskd Not tainted 4.19.0-rc2-next-20180904+ #55
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x48/0x88 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x151/0x192 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:144 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
watchdog+0xb39/0x1040 kernel/hung_task.c:265
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 18 Comm: kworker/1:0 Not tainted 4.19.0-rc2-next-20180904+ #55
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: rcu_gp process_srcu
RIP: 0010:rdtsc arch/x86/include/asm/msr.h:205 [inline]
RIP: 0010:rdtsc_ordered arch/x86/include/asm/msr.h:232 [inline]
RIP: 0010:delay_tsc+0x26/0x70 arch/x86/lib/delay.c:61
Code: 1f 44 00 00 55 65 ff 05 58 d2 2d 79 48 89 e5 65 8b 35 ae 65 2d 79 0f
ae e8 0f 31 48 c1 e2 20 48 89 d1 48 09 c1 0f ae e8 0f 31 <48> c1 e2 20 48
09 d0 48 89 c2 48 29 ca 48 39 fa 73 25 65 ff 0d 21
RSP: 0018:ffff8801d9f5f140 EFLAGS: 00000246
RAX: 00000000f6a2b2c8 RBX: dffffc0000000000 RCX: 000000f3f6a296fc
RDX: 00000000000000f3 RSI: 0000000000000001 RDI: 0000000000002ced
RBP: ffff8801d9f5f140 R08: ffff8801d9f504c0 R09: 0000000000000005
R10: 1ffffd1ffffba200 R11: ffffc90001945b87 R12: 0000000000000001
R13: ffffc900019457e0 R14: ffffc900019457e0 R15: ffff8801d9f5f2c8
FS: 0000000000000000(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7119f1f140 CR3: 00000001bef14000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__delay arch/x86/lib/delay.c:161 [inline]
__const_udelay+0x61/0x80 arch/x86/lib/delay.c:175
try_check_zero+0x36f/0x5d0 kernel/rcu/srcutree.c:721
srcu_advance_state kernel/rcu/srcutree.c:1155 [inline]
process_srcu+0x6dc/0x14a0 kernel/rcu/srcutree.c:1249
process_one_work+0xc73/0x1aa0 kernel/workqueue.c:2153
worker_thread+0x189/0x13c0 kernel/workqueue.c:2296
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:415
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot
May 18, 2019, 7:46:05 AM5/18/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