From: syzbot <syzbot+bb2e19a1190a556c01b1@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [cgroups?] INFO: task hung in cgroup_subtree_control_write (2)
Date: Mon, 15 Jun 2026 16:54:01 -0700 [thread overview]
Message-ID: <6a309099.428ffe26.258b27.016f.GAE@google.com> (raw)
In-Reply-To: <20260615232838.1858-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
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`
Tested on:
commit: 8d6dbbbe Add linux-next specific files for 20260615
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=d0d1fa2afcbce17c
dashboard link: https://syzkaller.appspot.com/bug?extid=bb2e19a1190a556c01b1
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=16af8bd2580000
prev parent reply other threads:[~2026-06-15 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 4:40 [syzbot] [cgroups?] INFO: task hung in cgroup_subtree_control_write (2) syzbot
2026-06-15 8:05 ` syzbot
2026-06-15 11:48 ` Hillf Danton
2026-06-15 15:47 ` syzbot
2026-06-15 23:28 ` Hillf Danton
2026-06-15 23:54 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a309099.428ffe26.258b27.016f.GAE@google.com \
--to=syzbot+bb2e19a1190a556c01b1@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.