[moderation] [kernel?] KCSAN: data-race in mas_wmb_replace / mtree_load

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 48a5a7ab8d6a Merge tag 'v7.2-rc4-smb3-client-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17edd746580000
kernel config: https://syzkaller.appspot.com/x/.config?x=84b3039e8461eef5
dashboard link: https://syzkaller.appspot.com/bug?extid=0d74f91215c2017478aa
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
CC: [linux-...@vger.kernel.org tg...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f80e802da100/disk-48a5a7ab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c52d5cfe5b19/vmlinux-48a5a7ab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/117a746cd695/bzImage-48a5a7ab.xz

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

sd 0:0:1:0: [sda] Synchronizing SCSI cache
virtio_scsi virtio0: 1/0/0 default/read/poll queues
==================================================================
BUG: KCSAN: data-race in mas_wmb_replace / mtree_load

write to 0xffff8881049bb600 of 8 bytes by task 3612 on cpu 0:
mte_set_node_dead lib/maple_tree.c:299 [inline]
mas_put_in_tree lib/maple_tree.c:1579 [inline]
mas_topiary_replace lib/maple_tree.c:1823 [inline]
mas_wmb_replace+0x22e/0x1770 lib/maple_tree.c:2083
mas_wr_store_entry+0x54a7/0x5a90 lib/maple_tree.c:-1
mas_store_gfp+0x5cd/0x6c0 lib/maple_tree.c:4905
irq_insert_desc kernel/irq/irqdesc.c:195 [inline]
alloc_descs kernel/irq/irqdesc.c:531 [inline]
__irq_alloc_descs+0x361/0x4d0 kernel/irq/irqdesc.c:922
irq_domain_alloc_descs kernel/irq/irqdomain.c:-1 [inline]
irq_domain_alloc_irqs_locked+0x89/0x6d0 kernel/irq/irqdomain.c:1639
__irq_domain_alloc_irqs+0x80/0xd0 kernel/irq/irqdomain.c:1711
__msi_domain_alloc_irqs+0x435/0xa00 kernel/irq/msi.c:1336
__msi_domain_alloc_locked kernel/irq/msi.c:1393 [inline]
msi_domain_alloc_locked+0x357/0x3e0 kernel/irq/msi.c:1398
msi_domain_alloc_irqs_all_locked+0xd2/0x110 kernel/irq/msi.c:1474
pci_msi_setup_msi_irqs+0x7a/0x90 drivers/pci/msi/irqdomain.c:17
__msix_setup_interrupts drivers/pci/msi/msi.c:687 [inline]
msix_setup_interrupts drivers/pci/msi/msi.c:708 [inline]
msix_capability_init+0x566/0x960 drivers/pci/msi/msi.c:748
__pci_enable_msix_range+0x41d/0x4b0 drivers/pci/msi/msi.c:856
pci_alloc_irq_vectors_affinity+0xac/0x1e0 drivers/pci/msi/api.c:268
vp_request_msix_vectors drivers/virtio/virtio_pci_common.c:157 [inline]
vp_find_vqs_msix+0x3f0/0x8b0 drivers/virtio/virtio_pci_common.c:414
vp_find_vqs+0x4a/0x490 drivers/virtio/virtio_pci_common.c:524
virtio_find_vqs include/linux/virtio_config.h:298 [inline]
virtnet_find_vqs drivers/net/virtio_net.c:6473 [inline]
init_vqs+0x6f5/0xa20 drivers/net/virtio_net.c:6555
virtnet_restore_up drivers/net/virtio_net.c:5740 [inline]
virtnet_restore+0x35/0x750 drivers/net/virtio_net.c:7202
virtio_device_restore_priv+0x23c/0x410 drivers/virtio/virtio.c:633
virtio_device_restore+0x1a/0x30 drivers/virtio/virtio.c:680
virtio_pci_restore drivers/virtio/virtio_pci_common.c:621 [inline]
virtio_pci_resume+0xfa/0x140 drivers/virtio/virtio_pci_common.c:648
pci_pm_resume+0x160/0x340 drivers/pci/pci-driver.c:1042
dpm_run_callback+0x53/0x2f0 drivers/base/power/main.c:510
device_resume+0x76f/0x7a0 drivers/base/power/main.c:1178
async_resume+0x2c/0x40 drivers/base/power/main.c:1201
async_run_entry_fn+0x52/0x180 kernel/async.c:129
process_one_work kernel/workqueue.c:3322 [inline]
process_scheduled_works+0x4d4/0x9a0 kernel/workqueue.c:3405
worker_thread+0x569/0x750 kernel/workqueue.c:3486
kthread+0x221/0x270 kernel/kthread.c:436
ret_from_fork+0x146/0x330 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

read to 0xffff8881049bb600 of 8 bytes by task 3613 on cpu 1:
ma_dead_node lib/maple_tree.c:544 [inline]
mtree_lookup_walk lib/maple_tree.c:2988 [inline]
mtree_load+0x3fd/0x600 lib/maple_tree.c:5668
irq_to_desc+0x1a/0x30 kernel/irq/irqdesc.c:414
name_unique kernel/irq/proc.c:302 [inline]
register_handler_proc+0xb7/0x290 kernel/irq/proc.c:319
__setup_irq+0xc44/0x1360 kernel/irq/manage.c:1815
request_threaded_irq+0x22d/0x2c0 kernel/irq/manage.c:2183
request_irq include/linux/interrupt.h:176 [inline]
vp_find_one_vq_msix+0x1cb/0x300 drivers/virtio/virtio_pci_common.c:362
vp_find_vqs_msix+0x74c/0x8b0 drivers/virtio/virtio_pci_common.c:426
vp_find_vqs+0x4a/0x490 drivers/virtio/virtio_pci_common.c:524
virtio_find_vqs include/linux/virtio_config.h:298 [inline]
virtscsi_init+0x50b/0x8b0 drivers/scsi/virtio_scsi.c:886
virtscsi_restore+0x3a/0xf0 drivers/scsi/virtio_scsi.c:1025
virtio_device_restore_priv+0x23c/0x410 drivers/virtio/virtio.c:633
virtio_device_restore+0x1a/0x30 drivers/virtio/virtio.c:680
virtio_pci_restore drivers/virtio/virtio_pci_common.c:621 [inline]
virtio_pci_resume+0xfa/0x140 drivers/virtio/virtio_pci_common.c:648
pci_pm_resume+0x160/0x340 drivers/pci/pci-driver.c:1042
dpm_run_callback+0x53/0x2f0 drivers/base/power/main.c:510
device_resume+0x76f/0x7a0 drivers/base/power/main.c:1178
async_resume+0x2c/0x40 drivers/base/power/main.c:1201
async_run_entry_fn+0x52/0x180 kernel/async.c:129
process_one_work kernel/workqueue.c:3322 [inline]
process_scheduled_works+0x4d4/0x9a0 kernel/workqueue.c:3405
worker_thread+0x569/0x750 kernel/workqueue.c:3486
kthread+0x221/0x270 kernel/kthread.c:436
ret_from_fork+0x146/0x330 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

value changed: 0xffffffff86d44821 -> 0xffff8881049bb600

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3613 Comm: kworker/u8:18 Not tainted syzkaller #0 PREEMPT(lazy)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Workqueue: async async_run_entry_fn
==================================================================


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