[moderation] [virtualization?] KCSAN: data-race in virtqueue_disable_cb / virtqueue_disable_cb (3)

0 views
Skip to first unread message

syzbot

unread,
Mar 26, 2024, 3:01:27 PMMar 26
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 928a87efa423 Merge tag 'gfs2-v6.8-fix' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c17b4e180000
kernel config: https://syzkaller.appspot.com/x/.config?x=aa27611f143168c9
dashboard link: https://syzkaller.appspot.com/bug?extid=cd8b274d0242a10bc4b9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [jaso...@redhat.com linux-...@vger.kernel.org m...@redhat.com virtual...@lists.linux.dev xuan...@linux.alibaba.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/aaed8a3c54cc/disk-928a87ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4b57f9e2e4e0/vmlinux-928a87ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dbcf18587d54/bzImage-928a87ef.xz

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

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

read to 0xffff888102201178 of 2 bytes by interrupt on cpu 0:
virtqueue_disable_cb_split drivers/virtio/virtio_ring.c:885 [inline]
virtqueue_disable_cb+0x63/0x180 drivers/virtio/virtio_ring.c:2446
skb_xmit_done+0x5f/0x140 drivers/net/virtio_net.c:533
vring_interrupt+0x157/0x180 drivers/virtio/virtio_ring.c:2595
__handle_irq_event_percpu+0x95/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+0x16d/0x5b0 kernel/irq/chip.c:831
generic_handle_irq_desc include/linux/irqdesc.h:161 [inline]
handle_irq arch/x86/kernel/irq.c:238 [inline]
__common_interrupt+0x58/0xf0 arch/x86/kernel/irq.c:257
common_interrupt+0x3e/0x90 arch/x86/kernel/irq.c:247
asm_common_interrupt+0x26/0x40 arch/x86/include/asm/idtentry.h:693

write to 0xffff888102201178 of 2 bytes by task 3073 on cpu 1:
virtqueue_disable_cb_split drivers/virtio/virtio_ring.c:886 [inline]
virtqueue_disable_cb+0x85/0x180 drivers/virtio/virtio_ring.c:2446
start_xmit+0x125/0xb60 drivers/net/virtio_net.c:2415
__netdev_start_xmit include/linux/netdevice.h:4903 [inline]
netdev_start_xmit include/linux/netdevice.h:4917 [inline]
xmit_one net/core/dev.c:3531 [inline]
dev_hard_start_xmit+0x119/0x3f0 net/core/dev.c:3547
sch_direct_xmit+0x1b0/0x580 net/sched/sch_generic.c:343
__dev_xmit_skb net/core/dev.c:3760 [inline]
__dev_queue_xmit+0xe88/0x1dd0 net/core/dev.c:4301
dev_queue_xmit include/linux/netdevice.h:3091 [inline]
neigh_hh_output include/net/neighbour.h:526 [inline]
neigh_output include/net/neighbour.h:540 [inline]
ip_finish_output2+0x73b/0x8b0 net/ipv4/ip_output.c:235
ip_finish_output+0x11a/0x2a0 net/ipv4/ip_output.c:323
NF_HOOK_COND include/linux/netfilter.h:303 [inline]
ip_output+0xab/0x170 net/ipv4/ip_output.c:433
dst_output include/net/dst.h:450 [inline]
ip_local_out net/ipv4/ip_output.c:129 [inline]
__ip_queue_xmit+0xbca/0xbf0 net/ipv4/ip_output.c:535
ip_queue_xmit+0x38/0x50 net/ipv4/ip_output.c:549
__tcp_transmit_skb+0x15b0/0x1970 net/ipv4/tcp_output.c:1462
tcp_transmit_skb net/ipv4/tcp_output.c:1480 [inline]
tcp_write_xmit+0x12dd/0x2ff0 net/ipv4/tcp_output.c:2792
__tcp_push_pending_frames+0x6a/0x1a0 net/ipv4/tcp_output.c:2977
tcp_push+0x320/0x340 net/ipv4/tcp.c:738
tcp_sendmsg_locked+0x21c9/0x26c0 net/ipv4/tcp.c:1310
tcp_sendmsg+0x30/0x50 net/ipv4/tcp.c:1342
inet_sendmsg+0x77/0xd0 net/ipv4/af_inet.c:851
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg+0x102/0x180 net/socket.c:745
sock_write_iter+0x164/0x1b0 net/socket.c:1160
call_write_iter include/linux/fs.h:2108 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0x771/0x8e0 fs/read_write.c:590
ksys_write+0xeb/0x1b0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:652
do_syscall_64+0xd3/0x1d0
entry_SYSCALL_64_after_hwframe+0x6d/0x75

value changed: 0x0000 -> 0x0001

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 3073 Comm: syz-fuzzer Tainted: G W 6.9.0-rc1-syzkaller-00005-g928a87efa423 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
==================================================================


---
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
Reply all
Reply to author
Forward
0 new messages