From: syzbot <syzbot+05f9cecd28e356241aba@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] INFO: task hung in new_device_store (5)
Date: Sat, 03 Jan 2026 03:24:02 -0800 [thread overview]
Message-ID: <6958fc52.050a0220.1c9965.000a.GAE@google.com> (raw)
In-Reply-To: <4b6af99a-7686-4e0d-815d-dc9a4e58687e@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: task hung in del_device_store
INFO: task syz-executor:7147 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:7147 tgid:7147 ppid:1 task_flags:0x400140 flags:0x00000011
Call trace:
__switch_to+0x418/0x87c arch/arm64/kernel/process.c:742 (T)
context_switch kernel/sched/core.c:5256 [inline]
__schedule+0x1250/0x2a7c kernel/sched/core.c:6863
__schedule_loop kernel/sched/core.c:6945 [inline]
schedule+0xb4/0x230 kernel/sched/core.c:6960
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:7017
__mutex_lock_common+0xd04/0x2678 kernel/locking/mutex.c:692
__mutex_lock kernel/locking/mutex.c:776 [inline]
mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:828
device_lock include/linux/device.h:895 [inline]
device_del+0xa4/0x808 drivers/base/core.c:3840
device_unregister+0x2c/0xf4 drivers/base/core.c:3919
nsim_bus_dev_del drivers/net/netdevsim/bus.c:483 [inline]
del_device_store+0x27c/0x31c drivers/net/netdevsim/bus.c:244
bus_attr_store+0x80/0xa4 drivers/base/bus.c:172
sysfs_kf_write+0x1a8/0x23c fs/sysfs/file.c:142
kernfs_fop_write_iter+0x33c/0x4d0 fs/kernfs/file.c:352
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x540/0xa3c fs/read_write.c:686
ksys_write+0x120/0x210 fs/read_write.c:738
__do_sys_write fs/read_write.c:749 [inline]
__se_sys_write fs/read_write.c:746 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:746
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
INFO: task syz-executor:7151 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:7151 tgid:7151 ppid:1 task_flags:0x400140 flags:0x00000001
Call trace:
__switch_to+0x418/0x87c arch/arm64/kernel/process.c:742 (T)
context_switch kernel/sched/core.c:5256 [inline]
__schedule+0x1250/0x2a7c kernel/sched/core.c:6863
__schedule_loop kernel/sched/core.c:6945 [inline]
schedule+0xb4/0x230 kernel/sched/core.c:6960
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:7017
__mutex_lock_common+0xd04/0x2678 kernel/locking/mutex.c:692
__mutex_lock kernel/locking/mutex.c:776 [inline]
mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:828
new_device_store+0x128/0x594 drivers/net/netdevsim/bus.c:184
bus_attr_store+0x80/0xa4 drivers/base/bus.c:172
sysfs_kf_write+0x1a8/0x23c fs/sysfs/file.c:142
kernfs_fop_write_iter+0x33c/0x4d0 fs/kernfs/file.c:352
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x540/0xa3c fs/read_write.c:686
ksys_write+0x120/0x210 fs/read_write.c:738
__do_sys_write fs/read_write.c:749 [inline]
__se_sys_write fs/read_write.c:746 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:746
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
INFO: task syz-executor:7155 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:7155 tgid:7155 ppid:1 task_flags:0x400140 flags:0x00000001
Call trace:
__switch_to+0x418/0x87c arch/arm64/kernel/process.c:742 (T)
context_switch kernel/sched/core.c:5256 [inline]
__schedule+0x1250/0x2a7c kernel/sched/core.c:6863
__schedule_loop kernel/sched/core.c:6945 [inline]
schedule+0xb4/0x230 kernel/sched/core.c:6960
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:7017
__mutex_lock_common+0xd04/0x2678 kernel/locking/mutex.c:692
__mutex_lock kernel/locking/mutex.c:776 [inline]
mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:828
del_device_store+0xd4/0x31c drivers/net/netdevsim/bus.c:234
bus_attr_store+0x80/0xa4 drivers/base/bus.c:172
sysfs_kf_write+0x1a8/0x23c fs/sysfs/file.c:142
kernfs_fop_write_iter+0x33c/0x4d0 fs/kernfs/file.c:352
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x540/0xa3c fs/read_write.c:686
ksys_write+0x120/0x210 fs/read_write.c:738
__do_sys_write fs/read_write.c:749 [inline]
__se_sys_write fs/read_write.c:746 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:746
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
INFO: task syz-executor:7162 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:7162 tgid:7162 ppid:1 task_flags:0x400140 flags:0x00000001
Call trace:
__switch_to+0x418/0x87c arch/arm64/kernel/process.c:742 (T)
context_switch kernel/sched/core.c:5256 [inline]
__schedule+0x1250/0x2a7c kernel/sched/core.c:6863
__schedule_loop kernel/sched/core.c:6945 [inline]
schedule+0xb4/0x230 kernel/sched/core.c:6960
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:7017
__mutex_lock_common+0xd04/0x2678 kernel/locking/mutex.c:692
__mutex_lock kernel/locking/mutex.c:776 [inline]
mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:828
del_device_store+0xd4/0x31c drivers/net/netdevsim/bus.c:234
bus_attr_store+0x80/0xa4 drivers/base/bus.c:172
sysfs_kf_write+0x1a8/0x23c fs/sysfs/file.c:142
kernfs_fop_write_iter+0x33c/0x4d0 fs/kernfs/file.c:352
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x540/0xa3c fs/read_write.c:686
ksys_write+0x120/0x210 fs/read_write.c:738
__do_sys_write fs/read_write.c:749 [inline]
__se_sys_write fs/read_write.c:746 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:746
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
Showing all locks held in the system:
3 locks held by kworker/u8:0/12:
#0: ffff0000c0032148 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff800097cf7be0 ((crda_timeout).work){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff800092ae4828 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80
2 locks held by kworker/1:0/24:
#0: ffff0000dbb87d48 ((wq_completion)wg-crypt-wg0){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff800097dc7be0 ((work_completion)(&peer->transmit_packet_work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
1 lock held by khungtaskd/32:
#0: ffff80008fa5b5a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire+0x4/0x48 include/linux/rcupdate.h:330
3 locks held by kworker/u8:2/41:
#0: ffff0000c0031948 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff800097fe7be0 ((work_completion)(&rdev->wiphy_work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff0000cefc8788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: class_wiphy_constructor include/net/cfg80211.h:6363 [inline]
#2: ffff0000cefc8788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: cfg80211_wiphy_work+0xd4/0x49c net/wireless/core.c:424
1 lock held by pr/ttyAMA-1/43:
#0: ffff80008f938118 (console_srcu){....}-{0:0}, at: rcu_try_lock_acquire+0x10/0x4c include/linux/rcupdate.h:335
3 locks held by kworker/u8:9/2250:
#0: ffff0000c0031948 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff8000a0a07be0 ((work_completion)(&rdev->wiphy_work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff0000f6ed8788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: class_wiphy_constructor include/net/cfg80211.h:6363 [inline]
#2: ffff0000f6ed8788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: cfg80211_wiphy_work+0xd4/0x49c net/wireless/core.c:424
3 locks held by kworker/u8:10/3212:
#0: ffff0000d49ef148 ((wq_completion)bat_events){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff8000a2fe7be0 ((work_completion)(&(&bat_priv->tt.work)->work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff80008fa5b5a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire+0x18/0x54 include/linux/rcupdate.h:330
3 locks held by kworker/u8:12/5293:
#0: ffff0000c0031948 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff80009e887be0 ((work_completion)(&rdev->wiphy_work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff0000f6e50788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: class_wiphy_constructor include/net/cfg80211.h:6363 [inline]
#2: ffff0000f6e50788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: cfg80211_wiphy_work+0xd4/0x49c net/wireless/core.c:424
3 locks held by kworker/u8:13/5389:
#0: ffff0000d503a948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff80009d2f7be0 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff800092ae4828 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80
2 locks held by kworker/u8:14/5595:
#0: ffff0000c0032148 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff80009ca37be0 ((work_completion)(&(&tbl->gc_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
7 locks held by kworker/u8:15/5638:
#0: ffff0000c1843148 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff80009c687be0 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff800092ad78d0 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xf0/0x638 net/core/net_namespace.c:670
#3: ffff0000ce0f70e8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
#3: ffff0000ce0f70e8 (&dev->mutex){....}-{4:4}, at: devl_dev_lock net/devlink/devl_internal.h:108 [inline]
#3: ffff0000ce0f70e8 (&dev->mutex){....}-{4:4}, at: devlink_pernet_pre_exit+0xe4/0x380 net/devlink/core.c:506
#4: ffff0000ce881250 (&devlink->lock_key#3){+.+.}-{4:4}, at: devl_lock net/devlink/core.c:276 [inline]
#4: ffff0000ce881250 (&devlink->lock_key#3){+.+.}-{4:4}, at: devl_dev_lock net/devlink/devl_internal.h:109 [inline]
#4: ffff0000ce881250 (&devlink->lock_key#3){+.+.}-{4:4}, at: devlink_pernet_pre_exit+0xf0/0x380 net/devlink/core.c:506
#5: ffff800092ae4828 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80
#6: ffff80008fb6f890 (remove_cache_srcu){.+.+}-{0:0}, at: srcu_lock_acquire+0x4/0x48 include/linux/srcu.h:184
1 lock held by udevd/6205:
#0: ffff80008fb6f890 (remove_cache_srcu){.+.+}-{0:0}, at: srcu_lock_acquire+0x4/0x48 include/linux/srcu.h:184
2 locks held by getty/6347:
#0: ffff0000d54830a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff800099f1e2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x34c/0xfc8 drivers/tty/n_tty.c:2211
1 lock held by syz-executor/6978:
#0: ffff80008fb6f890 (remove_cache_srcu){.+.+}-{0:0}, at: srcu_lock_acquire+0x4/0x48 include/linux/srcu.h:184
5 locks held by syz-executor/7147:
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2681 [inline]
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: vfs_write+0x24c/0xa3c fs/read_write.c:682
#1: ffff0000d983e888 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1b4/0x4d0 fs/kernfs/file.c:343
#2: ffff0000ccdf3968 (kn->active#55){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000ccdf3968 (kn->active#55){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x1f4/0x4d0 fs/kernfs/file.c:344
#3: ffff800091bf3b68 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd4/0x31c drivers/net/netdevsim/bus.c:234
#4: ffff0000ce0f70e8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
#4: ffff0000ce0f70e8 (&dev->mutex){....}-{4:4}, at: device_del+0xa4/0x808 drivers/base/core.c:3840
4 locks held by syz-executor/7151:
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2681 [inline]
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: vfs_write+0x24c/0xa3c fs/read_write.c:682
#1: ffff0000df93a088 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1b4/0x4d0 fs/kernfs/file.c:343
#2: ffff0000ccdf3878 (kn->active#56){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000ccdf3878 (kn->active#56){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x1f4/0x4d0 fs/kernfs/file.c:344
#3: ffff800091bf3b68 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: new_device_store+0x128/0x594 drivers/net/netdevsim/bus.c:184
4 locks held by syz-executor/7155:
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2681 [inline]
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: vfs_write+0x24c/0xa3c fs/read_write.c:682
#1: ffff0000ccc8ec88 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1b4/0x4d0 fs/kernfs/file.c:343
#2: ffff0000ccdf3968 (kn->active#55){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000ccdf3968 (kn->active#55){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x1f4/0x4d0 fs/kernfs/file.c:344
#3: ffff800091bf3b68 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd4/0x31c drivers/net/netdevsim/bus.c:234
4 locks held by syz-executor/7162:
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2681 [inline]
#0: ffff0000db97e420 (sb_writers#6){.+.+}-{0:0}, at: vfs_write+0x24c/0xa3c fs/read_write.c:682
#1: ffff0000ee505488 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1b4/0x4d0 fs/kernfs/file.c:343
#2: ffff0000ccdf3968 (kn->active#55){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000ccdf3968 (kn->active#55){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x1f4/0x4d0 fs/kernfs/file.c:344
#3: ffff800091bf3b68 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd4/0x31c drivers/net/netdevsim/bus.c:234
3 locks held by kworker/u8:16/7358:
#0: ffff0000c0031948 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
#1: ffff80009d4c7be0 ((work_completion)(&rdev->wiphy_work)){+.+.}-{0:0}, at: process_one_work+0x6d0/0x1558 kernel/workqueue.c:3231
#2: ffff0000d3700788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: class_wiphy_constructor include/net/cfg80211.h:6363 [inline]
#2: ffff0000d3700788 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: cfg80211_wiphy_work+0xd4/0x49c net/wireless/core.c:424
1 lock held by syz-executor/7366:
#0: ffff0000d5608ec0 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_open net/bluetooth/hci_core.c:428 [inline]
#0: ffff0000d5608ec0 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_open+0x19c/0x338 net/bluetooth/hci_core.c:486
1 lock held by syz-executor/7370:
#0: ffff80008fb6f890 (remove_cache_srcu){.+.+}-{0:0}, at: srcu_lock_acquire+0x4/0x48 include/linux/srcu.h:184
2 locks held by syz-executor/7372:
#0: ffff0000cc722280 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:353 [inline]
#0: ffff0000cc722280 (&mm->mmap_lock){++++}-{4:4}, at: __do_sys_brk mm/mmap.c:125 [inline]
#0: ffff0000cc722280 (&mm->mmap_lock){++++}-{4:4}, at: __se_sys_brk mm/mmap.c:115 [inline]
#0: ffff0000cc722280 (&mm->mmap_lock){++++}-{4:4}, at: __arm64_sys_brk+0x120/0x9c0 mm/mmap.c:115
#1: ffff80008fb6f890 (remove_cache_srcu){.+.+}-{0:0}, at: srcu_lock_acquire+0x4/0x48 include/linux/srcu.h:184
2 locks held by syz-executor/7375:
#0: ffff0000d9ae5118 (&data->open_mutex){+.+.}-{4:4}, at: vhci_create_device+0x3c/0x634 drivers/bluetooth/hci_vhci.c:478
#1: ffff80008fb6f890 (remove_cache_srcu){.+.+}-{0:0}, at: srcu_lock_acquire+0x4/0x48 include/linux/srcu.h:184
=============================================
Tested on:
commit: 805f9a06 Merge tag 'perf-tools-fixes-for-v6.19-2026-01..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13eaffb4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a8594efdc14f07a
dashboard link: https://syzkaller.appspot.com/bug?extid=05f9cecd28e356241aba
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=119cffb4580000
next prev parent reply other threads:[~2026-01-03 11:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 17:58 [syzbot] [net?] INFO: task hung in new_device_store (5) syzbot
2024-09-26 20:14 ` Eric Dumazet
2024-09-27 11:04 ` Hillf Danton
2024-09-27 11:24 ` Eric Dumazet
2024-09-27 11:27 ` Eric Dumazet
2024-09-27 11:41 ` Hillf Danton
2024-09-27 11:54 ` Eric Dumazet
2024-09-28 0:06 ` Hillf Danton
2024-10-09 8:20 ` syzbot
2025-12-25 16:24 ` syzbot
2025-12-29 6:36 ` Tetsuo Handa
2025-12-29 7:02 ` syzbot
2025-12-29 9:36 ` Tetsuo Handa
2025-12-29 12:22 ` syzbot
2025-12-29 14:18 ` Tetsuo Handa
2025-12-29 15:10 ` syzbot
2025-12-30 1:29 ` Tetsuo Handa
2025-12-30 2:08 ` syzbot
2025-12-30 3:07 ` Tetsuo Handa
2025-12-30 3:33 ` syzbot
2025-12-30 9:11 ` Hillf Danton
2025-12-30 9:38 ` syzbot
2025-12-30 13:24 ` Tetsuo Handa
2025-12-30 14:18 ` syzbot
2026-01-02 10:18 ` Tetsuo Handa
2026-01-02 10:53 ` syzbot
2026-01-03 9:59 ` Tetsuo Handa
2026-01-03 11:24 ` syzbot [this message]
2026-01-03 14:07 ` Tetsuo Handa
2026-01-03 14:33 ` syzbot
2025-12-30 7:48 ` Tetsuo Handa
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=6958fc52.050a0220.1c9965.000a.GAE@google.com \
--to=syzbot+05f9cecd28e356241aba@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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.