INFO: rcu detected stall in aead_recvmsg
6 مرّات مشاهدة
التخطي إلى أول رسالة غير مقروءة
syzbot
08/03/2019، 12:52:06 م8/3/2019
إلى syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 1fc1cd83 Merge branch 'for-5.1' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1775c2e7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=83f72881c3c30b7c
dashboard link: https://syzkaller.appspot.com/bug?extid=fb8495e60313270f1bcc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: amd64
CC: [a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net
je...@kernel.org ka...@fb.com linux-...@vger.kernel.org
net...@vger.kernel.org songliu...@fb.com y...@fb.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+fb8495...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (10499 ticks this GP) idle=ef6/1/0x4000000000000002
softirq=24557/24557 fqs=11
rcu: (t=10501 jiffies g=30241 q=258)
rcu: rcu_preempt kthread starved for 10480 jiffies! g30241 f0x0
RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt R running task 29168 10 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2877 [inline]
__schedule+0x817/0x1cc0 kernel/sched/core.c:3518
schedule+0x92/0x180 kernel/sched/core.c:3562
schedule_timeout+0x4db/0xfd0 kernel/time/timer.c:1803
rcu_gp_fqs_loop kernel/rcu/tree.c:1971 [inline]
rcu_gp_kthread+0x962/0x17b0 kernel/rcu/tree.c:2128
kthread+0x357/0x430 kernel/kthread.c:253
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
NMI backtrace for cpu 0
CPU: 0 PID: 13801 Comm: syz-executor.1 Not tainted 5.0.0+ #11
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1be/0x236 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_single_cpu_backtrace include/linux/nmi.h:164 [inline]
rcu_dump_cpu_stacks+0x183/0x1cf kernel/rcu/tree.c:1223
print_cpu_stall kernel/rcu/tree.c:1360 [inline]
check_cpu_stall kernel/rcu/tree.c:1434 [inline]
rcu_pending kernel/rcu/tree.c:3103 [inline]
rcu_sched_clock_irq.cold+0x500/0xa4a kernel/rcu/tree.c:2544
update_process_times+0x32/0x80 kernel/time/timer.c:1635
tick_sched_handle+0xa2/0x190 kernel/time/tick-sched.c:161
tick_sched_timer+0x47/0x130 kernel/time/tick-sched.c:1271
__run_hrtimer kernel/time/hrtimer.c:1389 [inline]
__hrtimer_run_queues+0x33e/0xde0 kernel/time/hrtimer.c:1451
hrtimer_interrupt+0x314/0x770 kernel/time/hrtimer.c:1509
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1035 [inline]
smp_apic_timer_interrupt+0x120/0x570 arch/x86/kernel/apic/apic.c:1060
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:807
</IRQ>
RIP: 0010:preempt_count_add+0x7b/0x1b0 kernel/sched/core.c:3239
Code: 00 00 fc ff df 48 89 da 83 e3 07 48 c1 ea 03 83 c3 03 65 44 01 25 75
39 b4 7e 0f b6 04 02 38 c3 7c 08 84 c0 0f 85 fe 00 00 00 <8b> 15 6f 25 0d
09 85 d2 75 15 65 8b 05 54 39 b4 7e 0f b6 c0 3d f4
RSP: 0018:ffff88805a9bf410 EFLAGS: 00000297 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000004 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 1ffffffff14b5b34 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff88805a9bf420 R08: 1ffff11015d05bc7 R09: ffffed1015d05bc8
R10: ffffed1015d05bc7 R11: ffff8880ae82de3b R12: 0000000000000001
R13: 0000000000000000 R14: ffff888097374700 R15: ffff88812c3f0ac0
is_module_text_address+0x13/0x4a kernel/module.c:4377
kernel_text_address+0x67/0xf0 kernel/extable.c:146
__kernel_text_address+0xd/0x40 kernel/extable.c:107
unwind_get_return_address arch/x86/kernel/unwind_frame.c:18 [inline]
unwind_get_return_address+0x61/0xa0 arch/x86/kernel/unwind_frame.c:13
__save_stack_trace+0x8a/0xf0 arch/x86/kernel/stacktrace.c:45
save_stack_trace+0x1a/0x20 arch/x86/kernel/stacktrace.c:60
save_stack+0x45/0xd0 mm/kasan/common.c:75
set_track mm/kasan/common.c:87 [inline]
__kasan_kmalloc mm/kasan/common.c:497 [inline]
__kasan_kmalloc.constprop.0+0xcf/0xe0 mm/kasan/common.c:470
kasan_slab_alloc+0xf/0x20 mm/kasan/common.c:505
slab_post_alloc_hook mm/slab.h:436 [inline]
slab_alloc mm/slab.c:3392 [inline]
__do_kmalloc mm/slab.c:3724 [inline]
__kmalloc+0x145/0x740 mm/slab.c:3735
kmalloc include/linux/slab.h:550 [inline]
sock_kmalloc net/core/sock.c:2121 [inline]
sock_kmalloc+0xc6/0x120 net/core/sock.c:2112
af_alg_alloc_areq+0x24/0x1e0 crypto/af_alg.c:1089
_aead_recvmsg crypto/algif_aead.c:157 [inline]
aead_recvmsg+0x45d/0x1ab0 crypto/algif_aead.c:334
sock_recvmsg_nosec net/socket.c:817 [inline]
sock_recvmsg net/socket.c:824 [inline]
sock_recvmsg+0xd0/0x110 net/socket.c:820
___sys_recvmsg+0x273/0x5a0 net/socket.c:2299
do_recvmmsg+0x27e/0x7a0 net/socket.c:2412
__sys_recvmmsg+0xe5/0x270 net/socket.c:2493
__do_sys_recvmmsg net/socket.c:2514 [inline]
__se_sys_recvmmsg net/socket.c:2507 [inline]
__x64_sys_recvmmsg+0xe6/0x140 net/socket.c:2507
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457f29
Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f88844b8c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 0000000000457f29
RDX: 0000000000000030 RSI: 0000000020007e00 RDI: 0000000000000008
RBP: 000000000073bf00 R08: 0000000020008000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f88844b96d4
R13: 00000000004c4c3e R14: 00000000004d8748 R15: 00000000ffffffff
---
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: 1fc1cd83 Merge branch 'for-5.1' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1775c2e7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=83f72881c3c30b7c
dashboard link: https://syzkaller.appspot.com/bug?extid=fb8495e60313270f1bcc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: amd64
CC: [a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net
je...@kernel.org ka...@fb.com linux-...@vger.kernel.org
net...@vger.kernel.org songliu...@fb.com y...@fb.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+fb8495...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (10499 ticks this GP) idle=ef6/1/0x4000000000000002
softirq=24557/24557 fqs=11
rcu: (t=10501 jiffies g=30241 q=258)
rcu: rcu_preempt kthread starved for 10480 jiffies! g30241 f0x0
RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: RCU grace-period kthread stack dump:
rcu_preempt R running task 29168 10 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2877 [inline]
__schedule+0x817/0x1cc0 kernel/sched/core.c:3518
schedule+0x92/0x180 kernel/sched/core.c:3562
schedule_timeout+0x4db/0xfd0 kernel/time/timer.c:1803
rcu_gp_fqs_loop kernel/rcu/tree.c:1971 [inline]
rcu_gp_kthread+0x962/0x17b0 kernel/rcu/tree.c:2128
kthread+0x357/0x430 kernel/kthread.c:253
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
NMI backtrace for cpu 0
CPU: 0 PID: 13801 Comm: syz-executor.1 Not tainted 5.0.0+ #11
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1be/0x236 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_single_cpu_backtrace include/linux/nmi.h:164 [inline]
rcu_dump_cpu_stacks+0x183/0x1cf kernel/rcu/tree.c:1223
print_cpu_stall kernel/rcu/tree.c:1360 [inline]
check_cpu_stall kernel/rcu/tree.c:1434 [inline]
rcu_pending kernel/rcu/tree.c:3103 [inline]
rcu_sched_clock_irq.cold+0x500/0xa4a kernel/rcu/tree.c:2544
update_process_times+0x32/0x80 kernel/time/timer.c:1635
tick_sched_handle+0xa2/0x190 kernel/time/tick-sched.c:161
tick_sched_timer+0x47/0x130 kernel/time/tick-sched.c:1271
__run_hrtimer kernel/time/hrtimer.c:1389 [inline]
__hrtimer_run_queues+0x33e/0xde0 kernel/time/hrtimer.c:1451
hrtimer_interrupt+0x314/0x770 kernel/time/hrtimer.c:1509
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1035 [inline]
smp_apic_timer_interrupt+0x120/0x570 arch/x86/kernel/apic/apic.c:1060
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:807
</IRQ>
RIP: 0010:preempt_count_add+0x7b/0x1b0 kernel/sched/core.c:3239
Code: 00 00 fc ff df 48 89 da 83 e3 07 48 c1 ea 03 83 c3 03 65 44 01 25 75
39 b4 7e 0f b6 04 02 38 c3 7c 08 84 c0 0f 85 fe 00 00 00 <8b> 15 6f 25 0d
09 85 d2 75 15 65 8b 05 54 39 b4 7e 0f b6 c0 3d f4
RSP: 0018:ffff88805a9bf410 EFLAGS: 00000297 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000004 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 1ffffffff14b5b34 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff88805a9bf420 R08: 1ffff11015d05bc7 R09: ffffed1015d05bc8
R10: ffffed1015d05bc7 R11: ffff8880ae82de3b R12: 0000000000000001
R13: 0000000000000000 R14: ffff888097374700 R15: ffff88812c3f0ac0
is_module_text_address+0x13/0x4a kernel/module.c:4377
kernel_text_address+0x67/0xf0 kernel/extable.c:146
__kernel_text_address+0xd/0x40 kernel/extable.c:107
unwind_get_return_address arch/x86/kernel/unwind_frame.c:18 [inline]
unwind_get_return_address+0x61/0xa0 arch/x86/kernel/unwind_frame.c:13
__save_stack_trace+0x8a/0xf0 arch/x86/kernel/stacktrace.c:45
save_stack_trace+0x1a/0x20 arch/x86/kernel/stacktrace.c:60
save_stack+0x45/0xd0 mm/kasan/common.c:75
set_track mm/kasan/common.c:87 [inline]
__kasan_kmalloc mm/kasan/common.c:497 [inline]
__kasan_kmalloc.constprop.0+0xcf/0xe0 mm/kasan/common.c:470
kasan_slab_alloc+0xf/0x20 mm/kasan/common.c:505
slab_post_alloc_hook mm/slab.h:436 [inline]
slab_alloc mm/slab.c:3392 [inline]
__do_kmalloc mm/slab.c:3724 [inline]
__kmalloc+0x145/0x740 mm/slab.c:3735
kmalloc include/linux/slab.h:550 [inline]
sock_kmalloc net/core/sock.c:2121 [inline]
sock_kmalloc+0xc6/0x120 net/core/sock.c:2112
af_alg_alloc_areq+0x24/0x1e0 crypto/af_alg.c:1089
_aead_recvmsg crypto/algif_aead.c:157 [inline]
aead_recvmsg+0x45d/0x1ab0 crypto/algif_aead.c:334
sock_recvmsg_nosec net/socket.c:817 [inline]
sock_recvmsg net/socket.c:824 [inline]
sock_recvmsg+0xd0/0x110 net/socket.c:820
___sys_recvmsg+0x273/0x5a0 net/socket.c:2299
do_recvmmsg+0x27e/0x7a0 net/socket.c:2412
__sys_recvmmsg+0xe5/0x270 net/socket.c:2493
__do_sys_recvmmsg net/socket.c:2514 [inline]
__se_sys_recvmmsg net/socket.c:2507 [inline]
__x64_sys_recvmmsg+0xe6/0x140 net/socket.c:2507
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457f29
Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f88844b8c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 0000000000457f29
RDX: 0000000000000030 RSI: 0000000020007e00 RDI: 0000000000000008
RBP: 000000000073bf00 R08: 0000000020008000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f88844b96d4
R13: 00000000004c4c3e R14: 00000000004d8748 R15: 00000000ffffffff
---
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
25/10/2019، 10:11:05 ص25/10/2019
إلى 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.
الرد على الكل
رد على الكاتب
إعادة توجيه
0 رسالة جديدة