================================================================== BUG: KCSAN: data-race in 0x0 / ns_capable_noaudit read to 0xffff88810484b3ec of 4 bytes by task 3299 on cpu 1: read-write to 0xffff88810484b3ec of 4 bytes by task 3299 on cpu 1: ns_capable_common kernel/capability.c:343 [inline] ns_capable_noaudit+0x83/0xb0 kernel/capability.c:380 net_ctl_permissions+0x3d/0x70 net/sysctl_net.c:48 sysctl_perm fs/proc/proc_sysctl.c:442 [inline] proc_sys_permission+0x126/0x260 fs/proc/proc_sysctl.c:817 do_inode_permission fs/namei.c:583 [inline] inode_permission+0x2b4/0x3c0 fs/namei.c:653 may_open+0x25b/0x350 fs/namei.c:4275 do_open fs/namei.c:4849 [inline] path_openat+0xb71/0x11e0 fs/namei.c:5016 do_file_open+0x16c/0x290 fs/namei.c:5045 do_sys_openat2+0xa1/0x140 fs/open.c:1443 do_sys_open fs/open.c:1449 [inline] __do_sys_openat fs/open.c:1465 [inline] __se_sys_openat fs/open.c:1460 [inline] __x64_sys_openat+0xf2/0x120 fs/open.c:1460 x64_sys_call+0x1f72/0x2550 arch/x86/include/generated/asm/syscalls_64.h:258 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f Reported by Kernel Concurrency Sanitizer on: CPU: 1 UID: 0 PID: 3299 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(lazy) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026 ================================================================== bridge0: port 1(bridge_slave_0) entered blocking state bridge0: port 1(bridge_slave_0) entered disabled state bridge_slave_0: entered allmulticast mode bridge_slave_0: entered promiscuous mode bridge0: port 2(bridge_slave_1) entered blocking state bridge0: port 2(bridge_slave_1) entered disabled state bridge_slave_1: entered allmulticast mode bridge_slave_1: entered promiscuous mode bond0: (slave bond_slave_0): Enslaving as an active interface with an up link bond0: (slave bond_slave_1): Enslaving as an active interface with an up link team0: Port device team_slave_0 added team0: Port device team_slave_1 added batman_adv: batadv0: Adding interface: batadv_slave_0 batman_adv: batadv0: The MTU of interface batadv_slave_0 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. batman_adv: batadv0: Not using interface batadv_slave_0 (retrying later): interface not active batman_adv: batadv0: Adding interface: batadv_slave_1 batman_adv: batadv0: The MTU of interface batadv_slave_1 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. batman_adv: batadv0: Not using interface batadv_slave_1 (retrying later): interface not active hsr_slave_0: entered promiscuous mode hsr_slave_1: entered promiscuous mode debugfs: 'hsr0' already exists in 'hsr' Cannot create hsr debugfs directory netdevsim netdevsim3 netdevsim0: renamed from eth0 8021q: adding VLAN 0 to HW filter on device netdevsim0 netdevsim netdevsim3 netdevsim1: renamed from eth1 8021q: adding VLAN 0 to HW filter on device netdevsim1 netdevsim netdevsim3 netdevsim2: renamed from eth2 8021q: adding VLAN 0 to HW filter on device netdevsim2 netdevsim netdevsim3 netdevsim3: renamed from eth3 8021q: adding VLAN 0 to HW filter on device netdevsim3 8021q: adding VLAN 0 to HW filter on device bond0 8021q: adding VLAN 0 to HW filter on device team0 hsr0: Slave B (hsr_slave_1) is not up; please bring it up to get a fully working HSR network 8021q: adding VLAN 0 to HW filter on device batadv0 veth0_vlan: entered promiscuous mode veth1_vlan: entered promiscuous mode veth0_macvtap: entered promiscuous mode veth1_macvtap: entered promiscuous mode batman_adv: batadv0: Interface activated: batadv_slave_0 batman_adv: batadv0: Interface activated: batadv_slave_1 soft_limit_in_bytes is deprecated and will be removed. Writing any value to this file has no effect. Please report your usecase to linux-mm@kvack.org if you depend on this functionality.