[moderation] [net?] KCSAN: data-race in __dev_change_flags / is_upper_ndev_bond_master_filter (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f03359bca01b Merge tag 'for-6.9-rc6-tag' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11b24e4b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c3beef2aff822313
dashboard link: https://syzkaller.appspot.com/bug?extid=400da2af10bda7e85eff
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [da...@davemloft.net edum...@google.com ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org pab...@redhat.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7f02c8b05997/disk-f03359bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6e4754c94ec3/vmlinux-f03359bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6da938ac63a4/bzImage-f03359bc.xz

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

==================================================================
BUG: KCSAN: data-race in __dev_change_flags / is_upper_ndev_bond_master_filter

read-write to 0xffff8881122980b0 of 4 bytes by task 9490 on cpu 0:
__dev_change_flags+0x9a/0x410 net/core/dev.c:8666
rtnl_configure_link net/core/rtnetlink.c:3305 [inline]
rtnl_newlink_create net/core/rtnetlink.c:3502 [inline]
__rtnl_newlink net/core/rtnetlink.c:3714 [inline]
rtnl_newlink+0x121e/0x1690 net/core/rtnetlink.c:3727
rtnetlink_rcv_msg+0x82e/0x8e0 net/core/rtnetlink.c:6595
netlink_rcv_skb+0x12c/0x230 net/netlink/af_netlink.c:2559
rtnetlink_rcv+0x1c/0x30 net/core/rtnetlink.c:6613
netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]
netlink_unicast+0x58d/0x660 net/netlink/af_netlink.c:1361
netlink_sendmsg+0x5d3/0x6e0 net/netlink/af_netlink.c:1905
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg+0x140/0x180 net/socket.c:745
____sys_sendmsg+0x312/0x410 net/socket.c:2584
___sys_sendmsg net/socket.c:2638 [inline]
__sys_sendmsg+0x1e9/0x280 net/socket.c:2667
__do_sys_sendmsg net/socket.c:2676 [inline]
__se_sys_sendmsg net/socket.c:2674 [inline]
__x64_sys_sendmsg+0x46/0x50 net/socket.c:2674
x64_sys_call+0xae9/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:47
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff8881122980b0 of 4 bytes by task 8568 on cpu 1:
netif_is_bond_master include/linux/netdevice.h:5041 [inline]
is_upper_ndev_bond_master_filter+0x2b/0xb0 drivers/infiniband/core/roce_gid_mgmt.c:275
ib_enum_roce_netdev+0x124/0x1d0 drivers/infiniband/core/device.c:2312
ib_enum_all_roce_netdevs+0x8a/0x100 drivers/infiniband/core/device.c:2341
netdevice_event_work_handler+0x15b/0x3c0 drivers/infiniband/core/roce_gid_mgmt.c:627
process_one_work kernel/workqueue.c:3267 [inline]
process_scheduled_works+0x465/0x990 kernel/workqueue.c:3348
worker_thread+0x526/0x730 kernel/workqueue.c:3429
kthread+0x1d1/0x210 kernel/kthread.c:388
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0x00001002 -> 0x00004006

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 8568 Comm: kworker/u8:13 Not tainted 6.9.0-rc6-syzkaller-00131-gf03359bca01b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: gid-cache-wq netdevice_event_work_handler
==================================================================


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