KCSAN: data-race in virtqueue_disable_cb / vring_interrupt

8 views
Skip to first unread message

syzbot

unread,
Apr 24, 2022, 1:40:22 PM4/24/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 13bc32bad705 Merge tag 'drm-fixes-2022-04-23' of git://ano..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d71798f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=30f43a6ded7cebcd
dashboard link: https://syzkaller.appspot.com/bug?extid=1dc46d73e4c1b726ed95
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [jaso...@redhat.com linux-...@vger.kernel.org m...@redhat.com virtual...@lists.linux-foundation.org]

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

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

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

write to 0xffff88810319864a of 1 bytes by interrupt on cpu 1:
vring_interrupt+0x132/0x180 drivers/virtio/virtio_ring.c:2144
__handle_irq_event_percpu+0x92/0x400 kernel/irq/handle.c:158
handle_irq_event_percpu kernel/irq/handle.c:193 [inline]
handle_irq_event+0x60/0xf0 kernel/irq/handle.c:210
handle_edge_irq+0x17e/0x5a0 kernel/irq/chip.c:817
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq arch/x86/kernel/irq.c:231 [inline]
__common_interrupt+0x60/0x100 arch/x86/kernel/irq.c:250
common_interrupt+0x9a/0xc0 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x1e/0x40
native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
acpi_safe_halt drivers/acpi/processor_idle.c:115 [inline]
acpi_idle_do_entry drivers/acpi/processor_idle.c:556 [inline]
acpi_idle_enter+0x27b/0x300 drivers/acpi/processor_idle.c:691
cpuidle_enter_state+0x2ee/0x7a0 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x3c/0x60 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:155 [inline]
cpuidle_idle_call kernel/sched/idle.c:236 [inline]
do_idle+0x1b2/0x250 kernel/sched/idle.c:303
cpu_startup_entry+0x15/0x20 kernel/sched/idle.c:400
secondary_startup_64_no_verify+0xc4/0xcb

read to 0xffff88810319864a of 1 bytes by task 1814 on cpu 0:
virtqueue_disable_cb+0x17/0x160 drivers/virtio/virtio_ring.c:2008
start_xmit+0xd1/0xaf0 drivers/net/virtio_net.c:1766
__netdev_start_xmit include/linux/netdevice.h:4778 [inline]
netdev_start_xmit include/linux/netdevice.h:4792 [inline]
xmit_one+0x105/0x2f0 net/core/dev.c:3532
dev_hard_start_xmit+0x72/0x120 net/core/dev.c:3548
sch_direct_xmit+0x1ac/0x580 net/sched/sch_generic.c:342
__dev_xmit_skb+0x808/0xdb0 net/core/dev.c:3759
__dev_queue_xmit+0x569/0xf00 net/core/dev.c:4141
dev_queue_xmit+0x13/0x20 net/core/dev.c:4209
neigh_hh_output include/net/neighbour.h:533 [inline]
neigh_output include/net/neighbour.h:547 [inline]
ip_finish_output2+0x709/0x850 net/ipv4/ip_output.c:228
ip_finish_output+0xf3/0x250 net/ipv4/ip_output.c:316
NF_HOOK_COND include/linux/netfilter.h:296 [inline]
ip_output+0xf3/0x1a0 net/ipv4/ip_output.c:430
dst_output include/net/dst.h:451 [inline]
ip_local_out net/ipv4/ip_output.c:126 [inline]
__ip_queue_xmit+0xa2e/0xa50 net/ipv4/ip_output.c:532
ip_queue_xmit+0x34/0x40 net/ipv4/ip_output.c:546
__tcp_transmit_skb+0x12a8/0x1790 net/ipv4/tcp_output.c:1402
__tcp_send_ack+0x1dc/0x2e0 net/ipv4/tcp_output.c:3970
tcp_send_ack+0x23/0x30 net/ipv4/tcp_output.c:3976
tcp_cleanup_rbuf+0x1c7/0x310 net/ipv4/tcp.c:1589
tcp_recvmsg_locked+0x1139/0x1550 net/ipv4/tcp.c:2544
tcp_recvmsg+0x16a/0x4e0 net/ipv4/tcp.c:2574
inet_recvmsg+0xa3/0x210 net/ipv4/af_inet.c:850
sock_recvmsg_nosec net/socket.c:948 [inline]
sock_recvmsg net/socket.c:966 [inline]
sock_read_iter+0x19d/0x1e0 net/socket.c:1039
call_read_iter include/linux/fs.h:2044 [inline]
new_sync_read fs/read_write.c:401 [inline]
vfs_read+0x5a5/0x6a0 fs/read_write.c:482
ksys_read+0xe8/0x1a0 fs/read_write.c:620
__do_sys_read fs/read_write.c:630 [inline]
__se_sys_read fs/read_write.c:628 [inline]
__x64_sys_read+0x3e/0x50 fs/read_write.c:628
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1814 Comm: syz-fuzzer Tainted: G W 5.18.0-rc3-syzkaller-00218-g13bc32bad705-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


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

syzbot

unread,
Sep 29, 2023, 5:42:29 AM9/29/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages