EXT4-fs error (device loop2): ext4_readdir:264: inode #11: block 37: comm syz-executor: path /307/file1/lost+found: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_empty_dir:3120: inode #11: block 37: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=5120, inode=0, rec_len=1279, size=1024 fake=0 ================================================================== BUG: KCSAN: data-race in _prb_read_valid / data_alloc write to 0xffffffff8687b170 of 8 bytes by task 23330 on cpu 1: data_alloc+0x271/0x2b0 kernel/printk/printk_ringbuffer.c:1095 prb_reserve+0x808/0xaf0 kernel/printk/printk_ringbuffer.c:1669 vprintk_store+0x56d/0x860 kernel/printk/printk.c:2326 vprintk_emit+0x178/0x650 kernel/printk/printk.c:2426 vprintk_default+0x26/0x30 kernel/printk/printk.c:2465 vprintk+0x1d/0x30 kernel/printk/printk_safe.c:82 _printk+0x79/0xa0 kernel/printk/printk.c:2475 __netdev_printk+0x321/0x3e0 net/core/dev.c:12594 netdev_info+0x9b/0xd0 net/core/dev.c:12641 __dev_set_promiscuity+0x233/0x450 net/core/dev.c:9349 __dev_set_rx_mode+0x113/0x160 net/core/dev.c:-1 dev_uc_sync_multiple+0x1e0/0x210 net/core/dev_addr_lists.c:774 team_port_add drivers/net/team/team_core.c:1295 [inline] team_add_slave+0x152f/0x17c0 drivers/net/team/team_core.c:1977 do_set_master+0x38d/0x460 net/core/rtnetlink.c:2948 do_setlink+0xa43/0x2810 net/core/rtnetlink.c:3150 rtnl_changelink net/core/rtnetlink.c:3761 [inline] __rtnl_newlink net/core/rtnetlink.c:3920 [inline] rtnl_newlink+0xe75/0x12d0 net/core/rtnetlink.c:4057 rtnetlink_rcv_msg+0x5fe/0x6d0 net/core/rtnetlink.c:6946 netlink_rcv_skb+0x123/0x220 net/netlink/af_netlink.c:2552 rtnetlink_rcv+0x1c/0x30 net/core/rtnetlink.c:6973 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0x5bd/0x690 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x58b/0x6b0 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x142/0x180 net/socket.c:729 ____sys_sendmsg+0x31e/0x4e0 net/socket.c:2614 ___sys_sendmsg+0x17b/0x1d0 net/socket.c:2668 __sys_sendmsg net/socket.c:2700 [inline] __do_sys_sendmsg net/socket.c:2705 [inline] __se_sys_sendmsg net/socket.c:2703 [inline] __x64_sys_sendmsg+0xd4/0x160 net/socket.c:2703 x64_sys_call+0x191e/0x2ff0 arch/x86/include/generated/asm/syscalls_64.h:47 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f read to 0xffffffff8687b170 of 16 bytes by task 19220 on cpu 0: desc_read kernel/printk/printk_ringbuffer.c:482 [inline] desc_read_finalized_seq kernel/printk/printk_ringbuffer.c:1874 [inline] prb_read kernel/printk/printk_ringbuffer.c:1922 [inline] _prb_read_valid+0x1bc/0x920 kernel/printk/printk_ringbuffer.c:2113 desc_update_last_finalized kernel/printk/printk_ringbuffer.c:1515 [inline] prb_final_commit+0x136/0x1e0 kernel/printk/printk_ringbuffer.c:1782 vprintk_store+0x741/0x860 kernel/printk/printk.c:2352 vprintk_emit+0x178/0x650 kernel/printk/printk.c:2426 vprintk_default+0x26/0x30 kernel/printk/printk.c:2465 vprintk+0x1d/0x30 kernel/printk/printk_safe.c:82 _printk+0x79/0xa0 kernel/printk/printk.c:2475 __ext4_error_inode+0x30f/0x3f0 fs/ext4/super.c:839 __ext4_check_dir_entry+0x4ff/0x510 fs/ext4/dir.c:120 ext4_empty_dir+0x448/0x600 fs/ext4/namei.c:3119 ext4_rmdir+0x1df/0x640 fs/ext4/namei.c:3166 vfs_rmdir+0x276/0x330 fs/namei.c:4461 do_rmdir+0x178/0x440 fs/namei.c:4516 __do_sys_unlinkat fs/namei.c:4690 [inline] __se_sys_unlinkat fs/namei.c:4684 [inline] __x64_sys_unlinkat+0x86/0xb0 fs/namei.c:4684 x64_sys_call+0x2ede/0x2ff0 arch/x86/include/generated/asm/syscalls_64.h:264 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Reported by Kernel Concurrency Sanitizer on: CPU: 0 UID: 0 PID: 19220 Comm: syz-executor Not tainted 6.17.0-rc2-syzkaller-00028-gbe48bcf004f9 #0 PREEMPT(voluntary) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 ================================================================== EXT4-fs error (device loop2): ext4_readdir:264: inode #11: block 37: comm syz-executor: path /307/file1/lost+found: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_empty_dir:3120: inode #11: block 37: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=5120, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_readdir:264: inode #11: block 37: comm syz-executor: path /307/file1/lost+found: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_empty_dir:3120: inode #11: block 37: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=5120, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_readdir:264: inode #11: block 37: comm syz-executor: path /307/file1/lost+found: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_empty_dir:3120: inode #11: block 37: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=5120, inode=0, rec_len=1279, size=1024 fake=0 EXT4-fs error (device loop2): ext4_readdir:264: inode #11: block 37: comm syz-executor: path /307/file1/lost+found: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1279, size=1024 fake=0