[v6.1] INFO: task hung in ext4_quota_write

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4aa6747d9352 Linux 6.1.69
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1100b4a1e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3efadc69a1b0490
dashboard link: https://syzkaller.appspot.com/bug?extid=d59334a63a7e339b51d1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/31c5d5a5223e/disk-4aa6747d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/85c4938c28c7/vmlinux-4aa6747d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0fcb53eb57be/Image-4aa6747d.gz.xz

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

INFO: task syz-executor.5:6421 blocked for more than 143 seconds.
Not tainted 6.1.69-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:0 pid:6421 ppid:4266 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
io_schedule+0x8c/0x188 kernel/sched/core.c:8786
bit_wait_io+0x1c/0xac kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xcc/0x1e8 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x194/0x21c kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer+0x78/0xac fs/buffer.c:69
lock_buffer include/linux/buffer_head.h:397 [inline]
ext4_quota_write+0x36c/0x54c fs/ext4/super.c:7150
qtree_write_dquot+0x1dc/0x488 fs/quota/quota_tree.c:431
v2_write_dquot+0xf4/0x188 fs/quota/quota_v2.c:358
dquot_commit+0x14c/0x240 fs/quota/dquot.c:512
ext4_write_dquot+0x1b0/0x284 fs/ext4/super.c:6753
ext4_mark_dquot_dirty+0xe8/0x140 fs/ext4/super.c:6801
mark_dquot_dirty fs/quota/dquot.c:372 [inline]
mark_all_dquot_dirty fs/quota/dquot.c:410 [inline]
dquot_alloc_inode+0x594/0xb64 fs/quota/dquot.c:1838
ext4_xattr_inode_alloc_quota fs/ext4/xattr.c:883 [inline]
ext4_xattr_set_entry+0x958/0x3064 fs/ext4/xattr.c:1665
ext4_xattr_block_set+0x54c/0x2c64 fs/ext4/xattr.c:1920
ext4_xattr_set_handle+0xae8/0x1294 fs/ext4/xattr.c:2406
ext4_xattr_set+0x1dc/0x350 fs/ext4/xattr.c:2508
ext4_xattr_user_set+0xd4/0xfc fs/ext4/xattr_user.c:41
__vfs_setxattr+0x388/0x3a4 fs/xattr.c:182
__vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:216
__vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277
vfs_setxattr+0x1a8/0x344 fs/xattr.c:309
do_setxattr fs/xattr.c:594 [inline]
setxattr+0x230/0x294 fs/xattr.c:617
path_setxattr+0x17c/0x258 fs/xattr.c:636
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff8000159f4ef0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff8000159f56f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
6 locks held by kworker/1:1/24:
#0: ffff0000c466cd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff800019ef7c20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000d10a4190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
#2: ffff0000d10a4190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1ac/0x4360 drivers/usb/core/hub.c:5758
#3: ffff0000d10a7510 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3122 [inline]
#3: ffff0000d10a7510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5330 [inline]
#3: ffff0000d10a7510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5574 [inline]
#3: ffff0000d10a7510 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5730 [inline]
#3: ffff0000d10a7510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x1b88/0x4360 drivers/usb/core/hub.c:5812
#4: ffff0000d15fe068 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5331 [inline]
#4: ffff0000d15fe068 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5574 [inline]
#4: ffff0000d15fe068 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5730 [inline]
#4: ffff0000d15fe068 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x1bb0/0x4360 drivers/usb/core/hub.c:5812
#5: ffff8000172142d0 (ehci_cf_port_reset_rwsem){.+.+}-{3:3}, at: hub_port_reset+0x190/0x17ec drivers/usb/core/hub.c:2979
1 lock held by khungtaskd/28:
#0: ffff8000159f4d20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
1 lock held by udevd/3844:
2 locks held by getty/3987:
#0: ffff0000d7660098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bc902f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
6 locks held by syz-executor.5/6421:
#0: ffff0000c3ab0460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff00012e630400 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#1: ffff00012e630400 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:308
#2: ffff00012e6300c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff00012e6300c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x1e0/0x1294 fs/ext4/xattr.c:2321
#3: ffff800015b26308 (dquot_srcu){....}-{0:0}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:305
#4: ffff00012e5be0a8 (&dquot->dq_lock){+.+.}-{3:3}, at: dquot_commit+0x54/0x240 fs/quota/dquot.c:505
#5: ffff0000c3ab0208 (&s->s_dquot.dqio_sem){++++}-{3:3}, at: v2_write_dquot+0x84/0x188 fs/quota/quota_v2.c:356
3 locks held by udevd/6488:
2 locks held by kworker/u4:15/11708:
2 locks held by syz-executor.5/12975:
#0: ffff0000df272098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff0000df272130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:947 [inline]
#1: ffff0000df272130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:967 [inline]
#1: ffff0000df272130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x328/0x6f0 drivers/tty/tty_io.c:1089
5 locks held by syz-executor.3/12974:

=============================================



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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d93fa2c78854 Linux 5.15.145
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1716f379e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8eb25e663e3df1b9
dashboard link: https://syzkaller.appspot.com/bug?extid=2bd238d977f1d0183a7b

compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/45f65ff2a6ba/disk-d93fa2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/983a4d12af77/vmlinux-d93fa2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8864285a1d94/Image-d93fa2c7.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+2bd238...@syzkaller.appspotmail.com

INFO: task syz-executor.1:5218 blocked for more than 143 seconds.
Not tainted 5.15.145-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor.1 state:D stack: 0 pid: 5218 ppid: 4024 flags:0x00000005
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
io_schedule+0x8c/0x194 kernel/sched/core.c:8484
bit_wait_io+0x1c/0xac kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xcc/0x1f0 kernel/sched/wait_bit.c:90

out_of_line_wait_on_bit_lock+0x194/0x21c kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]

__lock_buffer+0x80/0xc0 fs/buffer.c:69
lock_buffer include/linux/buffer_head.h:402 [inline]
ext4_quota_write+0x378/0x564 fs/ext4/super.c:6561
qtree_write_dquot+0x1dc/0x488 fs/quota/quota_tree.c:422

v2_write_dquot+0xf4/0x188 fs/quota/quota_v2.c:358
dquot_commit+0x14c/0x240 fs/quota/dquot.c:512

ext4_write_dquot+0x1b0/0x284 fs/ext4/super.c:6164
ext4_mark_dquot_dirty+0xe8/0x140 fs/ext4/super.c:6212

mark_dquot_dirty fs/quota/dquot.c:372 [inline]
mark_all_dquot_dirty fs/quota/dquot.c:410 [inline]

dquot_alloc_inode+0x598/0xb88 fs/quota/dquot.c:1838
ext4_xattr_inode_alloc_quota fs/ext4/xattr.c:883 [inline]
ext4_xattr_set_entry+0x958/0x3094 fs/ext4/xattr.c:1665
ext4_xattr_block_set+0x55c/0x2d1c fs/ext4/xattr.c:1920
ext4_xattr_set_handle+0xb04/0x12d8 fs/ext4/xattr.c:2406
ext4_xattr_set+0x1dc/0x350 fs/ext4/xattr.c:2507

ext4_xattr_user_set+0xd4/0xfc fs/ext4/xattr_user.c:41
__vfs_setxattr+0x388/0x3a4 fs/xattr.c:182
__vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:216
__vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277

vfs_setxattr+0x1a8/0x344 fs/xattr.c:303
do_setxattr fs/xattr.c:588 [inline]
setxattr+0x250/0x2b4 fs/xattr.c:611
path_setxattr+0x17c/0x258 fs/xattr.c:630
__do_sys_setxattr fs/xattr.c:646 [inline]
__se_sys_setxattr fs/xattr.c:642 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:642
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:

1 lock held by khungtaskd/27:
#0: ffff800014ae15e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
3 locks held by kworker/u4:5/743:
5 locks held by kworker/1:2/1529:
#0: ffff0000c2958938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff800020a87c00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff0000cf004220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#2: ffff0000cf004220 (&dev->mutex){....}-{3:3}, at: hub_event+0x1b8/0x47d4 drivers/usb/core/hub.c:5751
#3: ffff0000dd1e9220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#3: ffff0000dd1e9220 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0xe4/0x7e8 drivers/usb/core/hub.c:2230
#4: ffff0000d73281a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#4: ffff0000d73281a8 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1044 [inline]
#4: ffff0000d73281a8 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0xbc/0x6ac drivers/base/dd.c:1259
2 locks held by getty/3724:
#0: ffff0000d28a7098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a33b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:7/4069:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001d1d7c00 ((work_completion)(&fw_work->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff800014992610 (umhelper_sem){++++}-{3:3}, at: usermodehelper_read_lock_wait+0x138/0x244 kernel/umh.c:249
2 locks held by kworker/1:7/4107:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001d227c00 (key_gc_work){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
6 locks held by syz-executor.1/5218:
#0: ffff0000c2f4e460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000df88d3b0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff0000df88d3b0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:302
#2: ffff0000df88d088 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff0000df88d088 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x1e0/0x12d8 fs/ext4/xattr.c:2321
#3: ffff800014bf8138 (dquot_srcu){....}-{0:0}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:268
#4: ffff00012b8940a8 (&dquot->dq_lock){+.+.}-{3:3}, at: dquot_commit+0x54/0x240 fs/quota/dquot.c:505
#5: ffff0000c2f4e208 (&s->s_dquot.dqio_sem){++++}-{3:3}, at: v2_write_dquot+0x84/0x188 fs/quota/quota_v2.c:356
4 locks held by kworker/u4:9/7790:
1 lock held by syz-executor.1/12685:
#0: ffff800014ae5af0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x54/0x4b0 kernel/rcu/tree.c:4039

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: a507f147e6f0 Linux 6.1.70
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=155a8929e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=af33470cb003e14e

dashboard link: https://syzkaller.appspot.com/bug?extid=d59334a63a7e339b51d1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16423829e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12acaf31e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7157b698190b/disk-a507f147.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/075d989b469b/vmlinux-a507f147.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f18b4225d20b/Image-a507f147.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/db697adfec00/mount_1.gz

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

INFO: task syz-executor168:4244 blocked for more than 143 seconds.
Not tainted 6.1.70-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor168 state:D stack:0 pid:4244 ppid:4243 flags:0x00000005

1 lock held by khungtaskd/28:
#0: ffff8000159f4d20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305

2 locks held by getty/3990:
#0: ffff0000d62ab098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bca02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
6 locks held by syz-executor168/4244:
#0: ffff0000d8066460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000df362c20 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#1: ffff0000df362c20 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:308
#2: ffff0000df3628e8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff0000df3628e8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x1e0/0x1294 fs/ext4/xattr.c:2321
#3: ffff800015b26388 (dquot_srcu){....}-{0:0}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:305
#4: ffff0000e28c80a8 (&dquot->dq_lock){+.+.}-{3:3}, at: dquot_commit+0x54/0x240 fs/quota/dquot.c:505
#5: ffff0000d8066208 (&s->s_dquot.dqio_sem){++++}-{3:3}, at: v2_write_dquot+0x84/0x188 fs/quota/quota_v2.c:356

=============================================



---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.