freebsd boot error: panic: scsi_action: ccb ADDR, func_code 0x6 should not be allocated from UMA zone

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: eec2e4ef tmpfs: reimplement the mtime scan to use the lazy..
git tree: https://github.com/freebsd/freebsd-src.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=163f1cfdd00000
dashboard link: https://syzkaller.appspot.com/bug?extid=2e9ce63919709feb3d1c

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

panic: scsi_action: ccb 0xffffffff831e9490, func_code 0x6 should not be allocated from UMA zone

cpuid = 0
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xffffffff831e9340
vpanic() at vpanic+0x1c7/frame 0xffffffff831e93a0
panic() at panic+0x43/frame 0xffffffff831e9400
scsi_dev_async() at scsi_dev_async/frame 0xffffffff831e9440
vtscsi_attach() at vtscsi_attach+0xaf2/frame 0xffffffff831e95a0
device_attach() at device_attach+0x478/frame 0xffffffff831e95e0
vtpci_legacy_probe_and_attach_child() at vtpci_legacy_probe_and_attach_child+0xe7/frame 0xffffffff831e9620
vtpci_legacy_attach() at vtpci_legacy_attach+0x2fd/frame 0xffffffff831e9690
device_attach() at device_attach+0x478/frame 0xffffffff831e96d0
device_probe_and_attach() at device_probe_and_attach+0xb0/frame 0xffffffff831e9710
bus_generic_attach() at bus_generic_attach+0x28/frame 0xffffffff831e9730
pci_attach() at pci_attach+0x13c/frame 0xffffffff831e9770
acpi_pci_attach() at acpi_pci_attach+0x21/frame 0xffffffff831e97c0
device_attach() at device_attach+0x478/frame 0xffffffff831e9800
device_probe_and_attach() at device_probe_and_attach+0xb0/frame 0xffffffff831e9840
bus_generic_attach() at bus_generic_attach+0x28/frame 0xffffffff831e9860
acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0x5c9/frame 0xffffffff831e98d0
device_attach() at device_attach+0x478/frame 0xffffffff831e9910
device_probe_and_attach() at device_probe_and_attach+0xb0/frame 0xffffffff831e9950
bus_generic_attach() at bus_generic_attach+0x28/frame 0xffffffff831e9970
acpi_attach() at acpi_attach+0x13ba/frame 0xffffffff831e9a80
device_attach() at device_attach+0x478/frame 0xffffffff831e9ac0
device_probe_and_attach() at device_probe_and_attach+0xb0/frame 0xffffffff831e9b00
bus_generic_attach() at bus_generic_attach+0x28/frame 0xffffffff831e9b20
device_attach() at device_attach+0x478/frame 0xffffffff831e9b60
device_probe_and_attach() at device_probe_and_attach+0xb0/frame 0xffffffff831e9ba0
bus_generic_new_pass() at bus_generic_new_pass+0x15e/frame 0xffffffff831e9be0
bus_set_pass() at bus_set_pass+0xe2/frame 0xffffffff831e9c20
configure() at configure+0x10/frame 0xffffffff831e9c40
mi_startup() at mi_startup+0x3ac/frame 0xffffffff831e9cb0
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x67: movq $0,0x163973e(%rip)
db>


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