BUG: soft lockup in inet_release (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14aefe13880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=af4f17cb868de851c845
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

IPv6: ADDRCONF(NETDEV_UP): vxcan11: link is not ready
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor.0:27923]
Modules linked in:
irq event stamp: 57870653
hardirqs last enabled at (57870652): [<ffffffff81549445>] seqcount_lockdep_reader_access include/linux/seqlock.h:83 [inline]
hardirqs last enabled at (57870652): [<ffffffff81549445>] read_seqcount_begin include/linux/seqlock.h:164 [inline]
hardirqs last enabled at (57870652): [<ffffffff81549445>] ktime_get+0x235/0x2f0 kernel/time/timekeeping.c:756
hardirqs last disabled at (57870653): [<ffffffff81003d00>] trace_hardirqs_off_thunk+0x1a/0x1c
softirqs last enabled at (2648): [<ffffffff86f355af>] ipt_do_table+0xccf/0x1820 net/ipv4/netfilter/ip_tables.c:358
softirqs last disabled at (2650): [<ffffffff86d42c8d>] lwtunnel_xmit_redirect include/net/lwtunnel.h:92 [inline]
softirqs last disabled at (2650): [<ffffffff86d42c8d>] ip_finish_output2+0x28d/0x15a0 net/ipv4/ip_output.c:214
CPU: 0 PID: 27923 Comm: syz-executor.0 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:789 [inline]
RIP: 0010:lock_release+0x429/0x8b0 kernel/locking/lockdep.c:3930
Code: 84 08 00 00 00 00 00 00 48 c1 e8 03 80 3c 10 00 0f 85 95 03 00 00 48 83 3d 7b 34 a6 08 00 0f 84 cc 01 00 00 48 8b 3c 24 57 9d <0f> 1f 44 00 00 48 b8 00 00 00 00 00 fc ff df 49 c7 04 04 00 00 00
RSP: 0018:ffff8880353d71b8 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff13e3051 RBX: ffff88804d2b84c0 RCX: 1ffff11009a571c7
RDX: dffffc0000000000 RSI: 0000000000000007 RDI: 0000000000000286
RBP: 0000000000000006 R08: ffffffff8c665018 R09: 0000000000000006
R10: 0000000000000000 R11: ffffffff8c66501b R12: 1ffff11006a7ae3a
R13: 05c148b6992ebacf R14: ffff88804d2b84c0 R15: 0000000000000007
FS: 00007f2d29221700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563111b12bd8 CR3: 0000000090361000 CR4: 00000000003406f0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
__raw_spin_unlock include/linux/spinlock_api_smp.h:150 [inline]
_raw_spin_unlock+0x17/0x40 kernel/locking/spinlock.c:176
spin_unlock include/linux/spinlock.h:369 [inline]
tcf_police_act+0x786/0xe60 net/sched/act_police.c:268
tcf_action_exec net/sched/act_api.c:618 [inline]
tcf_action_exec+0x160/0x400 net/sched/act_api.c:598
tcf_exts_exec include/net/pkt_cls.h:388 [inline]
basic_classify+0x184/0x2b0 net/sched/cls_basic.c:52
tcf_classify+0x120/0x3c0 net/sched/cls_api.c:979
prio_classify net/sched/sch_prio.c:46 [inline]
prio_enqueue+0x3bb/0x7a0 net/sched/sch_prio.c:78
__dev_xmit_skb net/core/dev.c:3494 [inline]
__dev_queue_xmit+0x140a/0x2e00 net/core/dev.c:3807
neigh_hh_output include/net/neighbour.h:491 [inline]
neigh_output include/net/neighbour.h:499 [inline]
ip_finish_output2+0xb6d/0x15a0 net/ipv4/ip_output.c:230
ip_finish_output+0xae9/0x10b0 net/ipv4/ip_output.c:318
NF_HOOK_COND include/linux/netfilter.h:278 [inline]
ip_output+0x203/0x5f0 net/ipv4/ip_output.c:406
dst_output include/net/dst.h:455 [inline]
ip_local_out+0xaf/0x170 net/ipv4/ip_output.c:125
__ip_queue_xmit+0x91e/0x1c10 net/ipv4/ip_output.c:507
__tcp_transmit_skb+0x1b9c/0x3400 net/ipv4/tcp_output.c:1148
tcp_transmit_skb net/ipv4/tcp_output.c:1164 [inline]
tcp_send_active_reset+0x456/0x8e0 net/ipv4/tcp_output.c:3142
tcp_close+0xaa3/0xfd0 net/ipv4/tcp.c:2388
inet_release+0xd7/0x1e0 net/ipv4/af_inet.c:427
__sock_release+0xcd/0x2a0 net/socket.c:599
sock_close+0x15/0x20 net/socket.c:1214
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
get_signal+0x1b64/0x1f70 kernel/signal.c:2400
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f2d2ad120d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2d29221168 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: 0000000000278000 RBX: 00007f2d2ae321f0 RCX: 00007f2d2ad120d9
RDX: ffffffffffffff60 RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00007f2d2ad6dae9 R08: 0000000000000000 R09: 0000000000000f06
R10: 000000000000f401 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe46ed371f R14: 00007f2d29221300 R15: 0000000000022000
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:60


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