EXT4-fs (loop5): encrypted files will use data=ordered instead of data journaling mode
==================================================================
BUG: KCSAN: data-race in pcpu_alloc_noprof / pcpu_free_area

read-write to 0xffffffff88be03ac of 4 bytes by task 3317 on cpu 1:
 pcpu_update_empty_pages mm/percpu.c:602 [inline]
 pcpu_block_update_hint_free mm/percpu.c:1044 [inline]
 pcpu_free_area+0x4dc/0x570 mm/percpu.c:1302
 free_percpu+0x1c6/0xb30 mm/percpu.c:2246
 xt_percpu_counter_free+0x63/0x80 net/netfilter/x_tables.c:1951
 cleanup_entry+0x195/0x1c0 net/ipv6/netfilter/ip6_tables.c:671
 __do_replace+0x470/0x580 net/ipv6/netfilter/ip6_tables.c:1099
 do_replace net/ipv6/netfilter/ip6_tables.c:1158 [inline]
 do_ip6t_set_ctl+0x820/0x8c0 net/ipv6/netfilter/ip6_tables.c:1644
 nf_setsockopt+0x195/0x1b0 net/netfilter/nf_sockopt.c:101
 ipv6_setsockopt+0x10f/0x130 net/ipv6/ipv6_sockglue.c:998
 tcp_setsockopt+0x93/0xb0 net/ipv4/tcp.c:4029
 sock_common_setsockopt+0x64/0x80 net/core/sock.c:3803
 do_sock_setsockopt net/socket.c:2334 [inline]
 __sys_setsockopt+0x1cc/0x240 net/socket.c:2357
 __do_sys_setsockopt net/socket.c:2366 [inline]
 __se_sys_setsockopt net/socket.c:2363 [inline]
 __x64_sys_setsockopt+0x66/0x80 net/socket.c:2363
 x64_sys_call+0x278d/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:55
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffffffff88be03ac of 4 bytes by task 6886 on cpu 0:
 pcpu_alloc_noprof+0x9b6/0x10a0 mm/percpu.c:1894
 alloc_and_link_pwqs kernel/workqueue.c:5451 [inline]
 __alloc_workqueue kernel/workqueue.c:5708 [inline]
 alloc_workqueue+0x700/0x1300 kernel/workqueue.c:5758
 __ext4_fill_super fs/ext4/super.c:5446 [inline]
 ext4_fill_super+0x2f8e/0x3a10 fs/ext4/super.c:5686
 get_tree_bdev_flags+0x29f/0x310 fs/super.c:1636
 get_tree_bdev+0x1f/0x30 fs/super.c:1659
 ext4_get_tree+0x1c/0x30 fs/ext4/super.c:5718
 vfs_get_tree+0x56/0x1e0 fs/super.c:1814
 do_new_mount+0x227/0x690 fs/namespace.c:3507
 path_mount+0x49b/0xb30 fs/namespace.c:3834
 do_mount fs/namespace.c:3847 [inline]
 __do_sys_mount fs/namespace.c:4057 [inline]
 __se_sys_mount+0x27c/0x2d0 fs/namespace.c:4034
 __x64_sys_mount+0x67/0x80 fs/namespace.c:4034
 x64_sys_call+0x203e/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:166
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000005 -> 0x00000006

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 6886 Comm: syz.5.1563 Not tainted 6.12.0-rc7-syzkaller-00070-g0a9b9d17f3a7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
==================================================================
EXT4-fs (loop5): 1 orphan inode deleted
EXT4-fs (loop5): 1 truncate cleaned up
EXT4-fs error (device loop5): ext4_search_dir:1505: inode #12: block 7: comm syz.5.1563: bad entry in directory: directory entry overrun - offset=0, inode=13, rec_len=784, size=56 fake=0
EXT4-fs (loop5): Remounting filesystem read-only