INFO: rcu detected stall in tw_timer_handler

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 14b58326 Linux 4.14.193
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1427d7fa900000
kernel config: https://syzkaller.appspot.com/x/.config?x=68ef0287ccbc3b42
dashboard link: https://syzkaller.appspot.com/bug?extid=f4e653430df95208dbfd
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f4e653...@syzkaller.appspotmail.com

INFO: rcu_preempt self-detected stall on CPU
0-...: (1 GPs behind) idle=fd6/140000000000002/0 softirq=173100/173101 fqs=1
(t=10500 jiffies g=44985 c=44984 q=230)
rcu_preempt kthread starved for 10498 jiffies! g44985 c44984 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=1
rcu_preempt R running task 29464 8 2 0x80000000
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_timeout+0x4af/0xe90 kernel/time/timer.c:1754
rcu_gp_kthread+0xc0a/0x1e60 kernel/rcu/tree.c:2255
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
NMI backtrace for cpu 0
CPU: 0 PID: 8331 Comm: syz-executor.0 Not tainted 4.14.193-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x17f lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:158 [inline]
rcu_dump_cpu_stacks+0x15f/0x19c kernel/rcu/tree.c:1396
print_cpu_stall kernel/rcu/tree.c:1542 [inline]
check_cpu_stall kernel/rcu/tree.c:1610 [inline]
__rcu_pending kernel/rcu/tree.c:3390 [inline]
rcu_pending kernel/rcu/tree.c:3452 [inline]
rcu_check_callbacks.cold+0x464/0xd99 kernel/rcu/tree.c:2792
update_process_times+0x28/0xa0 kernel/time/timer.c:1591
tick_sched_handle+0x7d/0x150 kernel/time/tick-sched.c:165
tick_sched_timer+0x92/0x200 kernel/time/tick-sched.c:1223
__run_hrtimer kernel/time/hrtimer.c:1223 [inline]
__hrtimer_run_queues+0x30b/0xc80 kernel/time/hrtimer.c:1287
hrtimer_interrupt+0x1e6/0x5e0 kernel/time/hrtimer.c:1321
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1075 [inline]
smp_apic_timer_interrupt+0x117/0x5e0 arch/x86/kernel/apic/apic.c:1100
apic_timer_interrupt+0x93/0xa0 arch/x86/entry/entry_64.S:793
RIP: 0010:check_preemption_disabled+0x30/0x240 lib/smp_processor_id.c:52
RSP: 0000:ffff8880aea07cf8 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff10
RAX: ffff888088762140 RBX: ffff888087b385d8 RCX: 0000000000000000
RDX: 0000000000000100 RSI: ffffffff873ec8e0 RDI: ffffffff86e45b80
RBP: ffffffff86e45b80 R08: ffffffff8a0970c0 R09: 00000000000426c0
R10: ffff888088762a18 R11: ffff888088762140 R12: 0000000000000000
R13: ffffffff873ec8e0 R14: 1ffff11015d40fd2 R15: 0000000000000000
tw_timer_handler+0xbb/0x140 net/ipv4/inet_timewait_sock.c:151
call_timer_fn+0x14a/0x650 kernel/time/timer.c:1280
expire_timers+0x232/0x4d0 kernel/time/timer.c:1319
__run_timers kernel/time/timer.c:1644 [inline]
run_timer_softirq+0x1d5/0x5a0 kernel/time/timer.c:1657
__do_softirq+0x254/0xa1d kernel/softirq.c:288
invoke_softirq kernel/softirq.c:368 [inline]
irq_exit+0x193/0x240 kernel/softirq.c:409
exiting_irq arch/x86/include/asm/apic.h:648 [inline]
smp_apic_timer_interrupt+0x141/0x5e0 arch/x86/kernel/apic/apic.c:1102
apic_timer_interrupt+0x93/0xa0 arch/x86/entry/entry_64.S:793
</IRQ>
RIP: 0010:alloc_vmap_area+0x2a1/0x7c0 mm/vmalloc.c:488
RSP: 0000:ffff8880616ff8d8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff10
RAX: 1ffff11014ba94a0 RBX: ffffc9000199a000 RCX: ffffc90005b06000
RDX: 0000000000031f87 RSI: ffffffff817f32d7 RDI: ffff8880a0eb3830
RBP: ffff8880a5d4a500 R08: ffffffff8a0a6a28 R09: 000000000004004c
R10: ffff8880887629f0 R11: ffff888088762140 R12: ffffc9000199c000
R13: ffffc900019bd000 R14: dffffc0000000000 R15: 0000000000001000
__get_vm_area_node+0x126/0x340 mm/vmalloc.c:1414
__vmalloc_node_range mm/vmalloc.c:1762 [inline]
__vmalloc_node mm/vmalloc.c:1818 [inline]
__vmalloc_node_flags mm/vmalloc.c:1832 [inline]
vmalloc+0x98/0x150 mm/vmalloc.c:1854
bpf_prog_calc_tag+0xa3/0x620 kernel/bpf/core.c:162
replace_map_fd_with_map_ptr kernel/bpf/verifier.c:4436 [inline]
bpf_check+0x3d3/0x18a0 kernel/bpf/verifier.c:5030
bpf_prog_load+0x626/0x1050 kernel/bpf/syscall.c:1057
SYSC_bpf kernel/bpf/syscall.c:1512 [inline]
SyS_bpf+0x1336/0x3590 kernel/bpf/syscall.c:1477
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45ce79
RSP: 002b:00007fd0bc170c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000001c40 RCX: 000000000045ce79
RDX: 0000000000000048 RSI: 00000000200054c0 RDI: 0000000000000005
RBP: 000000000118bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffcbda4fc8f R14: 00007fd0bc1719c0 R15: 000000000118bf2c


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.