[v6.6] INFO: task hung in evict

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a5df3a702b2c Linux 6.6.96
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14d3428c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2632deddafa957e8
dashboard link: https://syzkaller.appspot.com/bug?extid=f4dac58135af0f5ed37a
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9ba5b19f9f4d/disk-a5df3a70.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2cd779015729/vmlinux-a5df3a70.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b56fc39e5cb8/bzImage-a5df3a70.xz

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

INFO: task syz-executor:5785 blocked for more than 145 seconds.
Not tainted 6.6.96-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:21256 pid:5785 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x14e2/0x4580 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
folio_wait_bit_common+0x6eb/0xf70 mm/filemap.c:1329
__filemap_get_folio+0xbc/0xbc0 mm/filemap.c:1910
truncate_inode_pages_range+0x40a/0xf00 mm/truncate.c:376
evict+0x499/0x870 fs/inode.c:707
dispose_list fs/inode.c:738 [inline]
evict_inodes+0x460/0x690 fs/inode.c:786
generic_shutdown_super+0x97/0x2b0 fs/super.c:672
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe988b8fc57
RSP: 002b:00007fffc7604a18 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007fe988c10925 RCX: 00007fe988b8fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffc7604ad0
RBP: 00007fffc7604ad0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fffc7605b60
R13: 00007fe988c10925 R14: 00000000000173ae R15: 00007fffc7605ba0
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5549:
#0: ffff88802e37f0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
1 lock held by syz-executor/5785:
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by kworker/1:5/5833:
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc900047ffd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc900047ffd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
1 lock held by syz.3.393/7690:
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: __super_lock fs/super.c:58 [inline]
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: super_lock+0x167/0x360 fs/super.c:117
5 locks held by kworker/u4:20/8346:
#0: ffff888017873938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017873938 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc90005357d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc90005357d00 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#2: ffffffff8dfae950 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x136/0xb90 net/core/net_namespace.c:606
#3: ffffffff8dfbb748 (rtnl_mutex){+.+.}-{3:3}, at: ip_tunnel_delete_nets+0xcc/0x360 net/ipv4/ip_tunnel.c:1166
#4: ffffffff8cd35738 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#4: ffffffff8cd35738 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x448/0x830 kernel/rcu/tree_exp.h:1004
1 lock held by syz.9.604/8788:
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: __super_lock fs/super.c:58 [inline]
#0: ffff88802c5660e0 (&type->s_umount_key#58){++++}-{3:3}, at: super_lock+0x167/0x360 fs/super.c:117
1 lock held by rm/8796:

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.6.96-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf41/0xf80 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 7282 Comm: kworker/u4:9 Not tainted 6.6.96-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:unwind_get_return_address+0x4b/0xc0 arch/x86/kernel/unwind_orc.c:369
Code: e8 03 42 0f b6 04 30 84 c0 75 6e 8b 2b 31 ff 89 ee e8 b9 08 4b 00 85 ed 74 4a 48 83 c3 48 49 89 df 49 c1 ef 03 43 80 3c 37 00 <74> 08 48 89 df e8 cb b3 a3 00 48 8b 3b e8 c3 d4 1d 00 89 c5 31 ff
RSP: 0018:ffffc90004067580 EFLAGS: 00000246
RAX: ffffffff813a9157 RBX: ffffc900040675f0 RCX: 0000000000000000
RDX: ffff88802c513c00 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffff88802c513c00 R09: 0000000000000003
R10: 0000000000000004 R11: 0000000000000000 R12: ffffffff88639322
R13: ffffc900040679d0 R14: dffffc0000000000 R15: 1ffff9200080cebe
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005638dcbe7950 CR3: 000000000cb30000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
arch_stack_walk+0x11d/0x190 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0x9c/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:52
kasan_save_free_info+0x2e/0x50 mm/kasan/generic.c:522
____kasan_slab_free+0x126/0x1e0 mm/kasan/common.c:236
kasan_slab_free include/linux/kasan.h:164 [inline]
slab_free_hook mm/slub.c:1806 [inline]
slab_free_freelist_hook+0x130/0x1b0 mm/slub.c:1832
slab_free mm/slub.c:3816 [inline]
__kmem_cache_free+0xba/0x1f0 mm/slub.c:3829
skb_kfree_head net/core/skbuff.c:945 [inline]
skb_free_head net/core/skbuff.c:957 [inline]
skb_release_data+0x634/0x800 net/core/skbuff.c:987
skb_release_all net/core/skbuff.c:1053 [inline]
__kfree_skb net/core/skbuff.c:1067 [inline]
consume_skb+0xb2/0x110 net/core/skbuff.c:1283
nsim_dev_trap_report drivers/net/netdevsim/dev.c:821 [inline]
nsim_dev_trap_report_work+0x76f/0xb00 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: a5df3a702b2c Linux 6.6.96
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=12c59582580000

kernel config: https://syzkaller.appspot.com/x/.config?x=2632deddafa957e8
dashboard link: https://syzkaller.appspot.com/bug?extid=f4dac58135af0f5ed37a
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171fb28c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c59582580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9ba5b19f9f4d/disk-a5df3a70.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2cd779015729/vmlinux-a5df3a70.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b56fc39e5cb8/bzImage-a5df3a70.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/cc23c9d19841/mount_0.gz

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

INFO: task syz-executor:5919 blocked for more than 143 seconds.

Not tainted 6.6.96-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor state:D stack:21584 pid:5919 ppid:1 flags:0x00004004

Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x14e2/0x4580 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
folio_wait_bit_common+0x6eb/0xf70 mm/filemap.c:1329
__filemap_get_folio+0xbc/0xbc0 mm/filemap.c:1910
truncate_inode_pages_range+0x40a/0xf00 mm/truncate.c:376
evict+0x499/0x870 fs/inode.c:707
dispose_list fs/inode.c:738 [inline]

evict_inodes+0x5fe/0x690 fs/inode.c:792

generic_shutdown_super+0x97/0x2b0 fs/super.c:672
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2

RIP: 0033:0x7f0844f8fc57
RSP: 002b:00007ffc8bdd7168 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f0845010925 RCX: 00007f0844f8fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc8bdd7220
RBP: 00007ffc8bdd7220 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc8bdd82b0
R13: 00007f0845010925 R14: 00000000000268a8 R15: 00007ffc8bdd82f0

</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633

2 locks held by kworker/u4:10/2938:
1 lock held by syslogd/5143:
#0: ffff8880b8f3c458 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558
2 locks held by getty/5555:
#0: ffff88814c80c0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243

#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217

1 lock held by syz-executor/5919:
#0: ffff88802c9fa0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88802c9fa0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88802c9fa0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/5968:
#0: ffff88807e5c40e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807e5c40e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807e5c40e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/5996:
#0: ffff8880638f20e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880638f20e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880638f20e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/6018:
#0: ffff88802e3860e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88802e3860e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88802e3860e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/6039:
#0: ffff888060b960e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff888060b960e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff888060b960e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/6073:
#0: ffff88805d6dc0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88805d6dc0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88805d6dc0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/6100:
#0: ffff88805e23c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88805e23c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88805e23c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/6128:
#0: ffff88805d6d60e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88805d6d60e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88805d6d60e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.6.96-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf41/0xf80 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1

CPU: 1 PID: 22 Comm: ksoftirqd/1 Not tainted 6.6.96-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025

RIP: 0010:__find_rr_leaf+0x12e/0x6c0 net/ipv6/route.c:839
Code: 44 24 68 4c 89 7c 24 30 4d 85 ff 74 3c 49 8d 9e 80 00 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 28 84 c0 0f 85 7e 03 00 00 8b 1b <89> df 44 8b 64 24 44 44 89 e6 e8 33 3a 58 f8 44 39 e3 0f 85 07 04
RSP: 0018:ffffc900001c70c0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000100 RCX: ffff88801ca43c00
RDX: 0000000000000100 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900001c7218 R08: ffffc900001c7340 R09: ffffc900001c7350
R10: ffffc900001c71a0 R11: fffff52000038e36 R12: 1ffff11004cbe68a
R13: dffffc0000000000 R14: ffff888024a5dc00 R15: ffffc900001c7318

FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f5aba63fff0 CR3: 000000000cb30000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>

find_rr_leaf net/ipv6/route.c:891 [inline]
rt6_select net/ipv6/route.c:935 [inline]
fib6_table_lookup+0x3a0/0xa70 net/ipv6/route.c:2221
ip6_pol_route+0x22d/0x1160 net/ipv6/route.c:2257
pol_lookup_func include/net/ip6_fib.h:578 [inline]
fib6_rule_lookup+0x1d7/0x510 net/ipv6/fib6_rules.c:116
ip6_route_input_lookup net/ipv6/route.c:2326 [inline]
ip6_route_input+0x6cf/0xa50 net/ipv6/route.c:2622
ip6_rcv_finish+0x143/0x230 net/ipv6/ip6_input.c:77
NF_HOOK+0x303/0x390 include/linux/netfilter.h:304
__netif_receive_skb_one_core net/core/dev.c:5596 [inline]
__netif_receive_skb+0xcc/0x290 net/core/dev.c:5710
process_backlog+0x380/0x6e0 net/core/dev.c:6038
__napi_poll+0xc0/0x460 net/core/dev.c:6600
napi_poll net/core/dev.c:6667 [inline]
net_rx_action+0x5ea/0xbf0 net/core/dev.c:6803
handle_softirqs+0x280/0x820 kernel/softirq.c:578
run_ksoftirqd+0x9c/0xf0 kernel/softirq.c:950
smpboot_thread_fn+0x635/0xa00 kernel/smpboot.c:164

kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.