INFO: rcu detected stall in smp_call_function_many

20 views
Skip to first unread message

syzbot

unread,
Mar 25, 2018, 8:01:04 PM3/25/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot hit the following crash on upstream commit
bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +0000)
Merge tag 'pinctrl-v4.16-3' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=e0f63c28c647aad79bf7

Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6350022366986240
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-5034017172441945317
compiler: gcc (GCC) 7.1.1 20170620
user-space arch: i386
CC: [aaro...@intel.com adob...@gmail.com fred...@kernel.org
linux-...@vger.kernel.org mi...@kernel.org pet...@infradead.org
tg...@linutronix.de ying....@intel.com]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+e0f63c...@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.

INFO: rcu_sched detected stalls on CPUs/tasks:
(detected by 0, t=125002 jiffies, g=8986, c=8985, q=742)
All QSes seen, last rcu_sched kthread activity 125002
(4294863874-4294738872), jiffies_till_next_fqs=3, root ->qsmask 0x0
syz-executor2 R running task 24048 7324 4292 0x20020008
Call Trace:
<IRQ>
sched_show_task+0x4a3/0x5e0 kernel/sched/core.c:5271
print_other_cpu_stall+0x996/0x1090 kernel/rcu/tree.c:1480
check_cpu_stall.isra.61+0x6e6/0x15b0 kernel/rcu/tree.c:1598
__rcu_pending kernel/rcu/tree.c:3361 [inline]
rcu_pending kernel/rcu/tree.c:3423 [inline]
rcu_check_callbacks+0x238/0xd20 kernel/rcu/tree.c:2763
update_process_times+0x30/0x60 kernel/time/timer.c:1636
tick_sched_handle+0x85/0x160 kernel/time/tick-sched.c:162
tick_sched_timer+0x42/0x120 kernel/time/tick-sched.c:1194
__run_hrtimer kernel/time/hrtimer.c:1349 [inline]
__hrtimer_run_queues+0x39c/0xec0 kernel/time/hrtimer.c:1411
hrtimer_interrupt+0x2a5/0x6f0 kernel/time/hrtimer.c:1469
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1025 [inline]
smp_apic_timer_interrupt+0x14a/0x700 arch/x86/kernel/apic/apic.c:1050
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:857
</IRQ>
RIP: 0010:rep_nop arch/x86/include/asm/processor.h:657 [inline]
RIP: 0010:cpu_relax arch/x86/include/asm/processor.h:662 [inline]
RIP: 0010:csd_lock_wait kernel/smp.c:108 [inline]
RIP: 0010:smp_call_function_single+0x364/0x560 kernel/smp.c:302
RSP: 0018:ffff8801a9936be0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff12
RAX: 0000000000010000 RBX: 1ffff10035326d84 RCX: ffffffff8165f292
RDX: 0000000000010000 RSI: ffffc90003444000 RDI: ffff8801a9936cd8
RBP: ffff8801a9936d30 R08: 0000000000000000 R09: 1ffff10035326db6
R10: ffff8801a9936d50 R11: 0000000000000002 R12: ffff8801a9936cd8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffed0035326d90
smp_call_function_many+0x773/0x930 kernel/smp.c:434
smp_call_function kernel/smp.c:492 [inline]
on_each_cpu+0x3d/0x1b0 kernel/smp.c:602
flush_tlb_all+0x17/0x20 arch/x86/mm/tlb.c:659
__change_page_attr arch/x86/mm/pageattr.c:1303 [inline]
__change_page_attr_set_clr+0x4b7/0x2720 arch/x86/mm/pageattr.c:1391
cpa_process_alias arch/x86/mm/pageattr.c:1343 [inline]
__change_page_attr_set_clr+0x2036/0x2720 arch/x86/mm/pageattr.c:1398
change_page_attr_set_clr+0x40c/0xf60 arch/x86/mm/pageattr.c:1487
change_page_attr_clear arch/x86/mm/pageattr.c:1530 [inline]
set_memory_ro+0x2e/0x40 arch/x86/mm/pageattr.c:1759
bpf_prog_lock_ro include/linux/filter.h:632 [inline]
bpf_prog_select_runtime+0x189/0x5c0 kernel/bpf/core.c:1503
bpf_migrate_filter net/core/filter.c:1068 [inline]
bpf_prepare_filter+0x933/0xe40 net/core/filter.c:1116
__get_filter+0x1ae/0x220 net/core/filter.c:1309
sk_attach_filter+0x1d/0x80 net/core/filter.c:1324
sock_setsockopt+0x1680/0x1b10 net/core/sock.c:928
compat_sock_setsockopt.constprop.6+0xae/0x3d0 net/compat.c:383
C_SYSC_setsockopt net/compat.c:400 [inline]
compat_SyS_setsockopt+0x34a/0x410 net/compat.c:386
do_syscall_32_irqs_on arch/x86/entry/common.c:330 [inline]
do_fast_syscall_32+0x3ec/0xf9f arch/x86/entry/common.c:392
entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139
RIP: 0023:0xf7f93c99
RSP: 002b:00000000f778f09c EFLAGS: 00000286 ORIG_RAX: 000000000000016e
RAX: ffffffffffffffda RBX: 0000000000000014 RCX: 0000000000000001
RDX: 000000000000001a RSI: 0000000020c73000 RDI: 0000000000000010
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
rcu_sched kthread starved for 125002 jiffies! g8986 c8985 f0x2
RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=1
rcu_sched R running task 23448 8 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2862 [inline]
__schedule+0x8fb/0x1ec0 kernel/sched/core.c:3440
schedule+0xf5/0x430 kernel/sched/core.c:3499
schedule_timeout+0x118/0x230 kernel/time/timer.c:1801
rcu_gp_kthread+0x9dd/0x18e0 kernel/rcu/tree.c:2230
kthread+0x33c/0x400 kernel/kthread.c:238
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:406


---
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

Dmitry Vyukov

unread,
Dec 31, 2018, 2:57:20 AM12/31/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
This stopped happening 4+ months ago, let's prevent potential new
future crashes from merging into this

#syz invalid
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a114a8ef648ef8c05684578a4%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages