==================================================================
BUG: KCSAN: data-race in virtqueue_disable_cb / vring_interrupt

write to 0xffff8881032ad152 of 1 bytes by interrupt on cpu 1:
 vring_interrupt+0x128/0x170 drivers/virtio/virtio_ring.c:2497
 __handle_irq_event_percpu+0x91/0x490 kernel/irq/handle.c:158
 handle_irq_event_percpu kernel/irq/handle.c:193 [inline]
 handle_irq_event+0x64/0xf0 kernel/irq/handle.c:210
 handle_edge_irq+0x167/0x590 kernel/irq/chip.c:819
 generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
 handle_irq arch/x86/kernel/irq.c:231 [inline]
 __common_interrupt+0x3c/0xb0 arch/x86/kernel/irq.c:250
 common_interrupt+0x7a/0x90 arch/x86/kernel/irq.c:240
 asm_common_interrupt+0x26/0x40 arch/x86/include/asm/idtentry.h:636
 clear_page_erms+0xb/0x10 arch/x86/lib/clear_page_64.S:49
 clear_page arch/x86/include/asm/page_64.h:53 [inline]
 clear_highpage_kasan_tagged include/linux/highmem.h:248 [inline]
 kernel_init_pages mm/page_alloc.c:1237 [inline]
 post_alloc_hook mm/page_alloc.c:1729 [inline]
 prep_new_page+0x5a/0x180 mm/page_alloc.c:1738
 get_page_from_freelist+0x1306/0x1360 mm/page_alloc.c:3502
 __alloc_pages+0x193/0x340 mm/page_alloc.c:4768
 vma_alloc_folio+0x6a3/0x8c0 mm/mempolicy.c:2240
 wp_page_copy mm/memory.c:3070 [inline]
 do_wp_page+0x9e3/0x1fd0 mm/memory.c:3432
 handle_pte_fault mm/memory.c:4964 [inline]
 __handle_mm_fault mm/memory.c:5089 [inline]
 handle_mm_fault+0x5ba/0x2c60 mm/memory.c:5243
 do_user_addr_fault arch/x86/mm/fault.c:1349 [inline]
 handle_page_fault arch/x86/mm/fault.c:1534 [inline]
 exc_page_fault+0x256/0x780 arch/x86/mm/fault.c:1590
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

read to 0xffff8881032ad152 of 1 bytes by task 9498 on cpu 0:
 virtqueue_disable_cb_split drivers/virtio/virtio_ring.c:862 [inline]
 virtqueue_disable_cb+0x92/0x180 drivers/virtio/virtio_ring.c:2352
 start_xmit+0xf0/0xae0 drivers/net/virtio_net.c:2038
 __netdev_start_xmit include/linux/netdevice.h:4915 [inline]
 netdev_start_xmit include/linux/netdevice.h:4929 [inline]
 xmit_one net/core/dev.c:3578 [inline]
 dev_hard_start_xmit+0x11b/0x3f0 net/core/dev.c:3594
 sch_direct_xmit+0x1b0/0x570 net/sched/sch_generic.c:342
 __dev_xmit_skb net/core/dev.c:3805 [inline]
 __dev_queue_xmit+0xe5f/0x1d10 net/core/dev.c:4210
 dev_queue_xmit include/linux/netdevice.h:3085 [inline]
 neigh_hh_output include/net/neighbour.h:528 [inline]
 neigh_output include/net/neighbour.h:542 [inline]
 ip_finish_output2+0x700/0x840 net/ipv4/ip_output.c:229
 ip_finish_output+0xf4/0x240 net/ipv4/ip_output.c:317
 NF_HOOK_COND include/linux/netfilter.h:292 [inline]
 ip_output+0xe5/0x1b0 net/ipv4/ip_output.c:431
 dst_output include/net/dst.h:458 [inline]
 ip_local_out net/ipv4/ip_output.c:126 [inline]
 __ip_queue_xmit+0xa4d/0xa70 net/ipv4/ip_output.c:533
 ip_queue_xmit+0x38/0x40 net/ipv4/ip_output.c:547
 __tcp_transmit_skb+0x1194/0x16e0 net/ipv4/tcp_output.c:1399
 __tcp_send_ack+0x1de/0x2d0 net/ipv4/tcp_output.c:3983
 tcp_send_ack+0x27/0x30 net/ipv4/tcp_output.c:3989
 __tcp_cleanup_rbuf+0x149/0x260 net/ipv4/tcp.c:1621
 tcp_cleanup_rbuf net/ipv4/tcp.c:1632 [inline]
 tcp_recvmsg_locked+0x109d/0x1540 net/ipv4/tcp.c:2645
 tcp_recvmsg+0x13b/0x490 net/ipv4/tcp.c:2675
 inet_recvmsg+0xa2/0x210 net/ipv4/af_inet.c:861
 sock_recvmsg_nosec net/socket.c:1019 [inline]
 sock_recvmsg net/socket.c:1040 [inline]
 sock_read_iter+0x1a0/0x210 net/socket.c:1118
 call_read_iter include/linux/fs.h:1862 [inline]
 new_sync_read fs/read_write.c:389 [inline]
 vfs_read+0x3b7/0x580 fs/read_write.c:470
 ksys_read+0xeb/0x1a0 fs/read_write.c:613
 __do_sys_read fs/read_write.c:623 [inline]
 __se_sys_read fs/read_write.c:621 [inline]
 __x64_sys_read+0x42/0x50 fs/read_write.c:621
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 9498 Comm: syz-fuzzer Not tainted 6.4.0-rc4-syzkaller-00268-g51f269a6ecc7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
==================================================================