[syzbot] linux-next build error (26)

[syzbot] linux-next build error (26)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    4fa3f5fabb30 Add linux-next specific files for 20260616
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13c134ae580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3bf71f65d7d65ae1
dashboard link: https://syzkaller.appspot.com/bug?extid=1f14a35d0c73d31555e4
compiler:       Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

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

error[E0560]: struct `blk_mq_tag_set` has no field named `ops`
error[E0560]: struct `blk_mq_tag_set` has no field named `nr_hw_queues`
error[E0560]: struct `blk_mq_tag_set` has no field named `timeout`
error[E0560]: struct `blk_mq_tag_set` has no field named `numa_node`
error[E0560]: struct `blk_mq_tag_set` has no field named `queue_depth`
error[E0560]: struct `blk_mq_tag_set` has no field named `cmd_size`
error[E0560]: struct `blk_mq_tag_set` has no field named `flags`
error[E0560]: struct `blk_mq_tag_set` has no field named `driver_data`
error[E0560]: struct `blk_mq_tag_set` has no field named `nr_maps`
error[E0609]: no field `su_group` on type `configfs_subsystem`
error[E0609]: no field `su_mutex` on type `configfs_subsystem`
error[E0609]: no field `driver_data` on type `acpi_device_id`
error[E0609]: no field `id` on type `acpi_device_id`
error[E0609]: no field `parent` on type `bindings::device`
error[E0609]: no field `release` on type `bindings::device`
error[E0609]: no field `logical_block_size` on type `bindings::queue_limits`
error[E0609]: no field `physical_block_size` on type `bindings::queue_limits`
error[E0609]: no field `features` on type `bindings::queue_limits`
error[E0609]: no field `fops` on type `gendisk`
error[E0609]: no field `disk_name` on type `gendisk`

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