[v5.15] INFO: task hung in xfs_buf_delwri_pushbuf
0 views
Skip to first unread message
syzbot
Mar 14, 2023, 2:13:38 PM3/14/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 2ddbd0f967b3 Linux 5.15.102
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13827cecc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fec083380faceb1e
dashboard link: https://syzkaller.appspot.com/bug?extid=3ae67535b07c92aa02fd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156d2aa91f3c/disk-2ddbd0f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0e97f5be5fb/vmlinux-2ddbd0f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20d0a55a041d/bzImage-2ddbd0f9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ae675...@syzkaller.appspotmail.com
INFO: task syz-executor.2:4867 blocked for more than 143 seconds.
Not tainted 5.15.102-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:23072 pid: 4867 ppid: 3634 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x1348/0x4610 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
xfs_buf_iowait+0x138/0x5d0 fs/xfs/xfs_buf.c:1573
xfs_buf_delwri_pushbuf+0x34d/0x5a0 fs/xfs/xfs_buf.c:2251
xfs_qm_flush_one+0x266/0x350 fs/xfs/xfs_qm.c:1249
xfs_qm_dquot_walk+0x22a/0x4a0 fs/xfs/xfs_qm.c:86
xfs_qm_quotacheck+0x2f7/0x640 fs/xfs/xfs_qm.c:1335
xfs_qm_mount_quotas+0x328/0x610 fs/xfs/xfs_qm.c:1441
xfs_mountfs+0x162b/0x1ca0 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0x100c/0x1240 fs/xfs/xfs_super.c:1658
get_tree_bdev+0x3fe/0x620 fs/super.c:1294
vfs_get_tree+0x88/0x270 fs/super.c:1499
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f701c1d162a
RSP: 002b:00007f701a741f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00000000000095d1 RCX: 00007f701c1d162a
RDX: 0000000020000180 RSI: 0000000020009640 RDI: 00007f701a741fe0
RBP: 00007f701a742020 R08: 00007f701a742020 R09: 0000000000000090
R10: 0000000000000090 R11: 0000000000000202 R12: 0000000020000180
R13: 0000000020009640 R14: 00007f701a741fe0 R15: 0000000020000100
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/26:
#0: ffffffff8c91c2a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:4/1157:
2 locks held by getty/3270:
#0: ffff88814b1ae098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900020a32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
3 locks held by syz-executor.2/4867:
#0: ffff88802d01a0e0 (&type->s_umount_key#52/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff88802c940158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff88801efe1c78 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff88801efe1c78 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 26 Comm: khungtaskd Not tainted 5.15.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xf54/0xfa0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:109 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570
---
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.
syzbot found the following issue on:
HEAD commit: 2ddbd0f967b3 Linux 5.15.102
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13827cecc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fec083380faceb1e
dashboard link: https://syzkaller.appspot.com/bug?extid=3ae67535b07c92aa02fd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156d2aa91f3c/disk-2ddbd0f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0e97f5be5fb/vmlinux-2ddbd0f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20d0a55a041d/bzImage-2ddbd0f9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ae675...@syzkaller.appspotmail.com
INFO: task syz-executor.2:4867 blocked for more than 143 seconds.
Not tainted 5.15.102-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:23072 pid: 4867 ppid: 3634 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x1348/0x4610 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
xfs_buf_iowait+0x138/0x5d0 fs/xfs/xfs_buf.c:1573
xfs_buf_delwri_pushbuf+0x34d/0x5a0 fs/xfs/xfs_buf.c:2251
xfs_qm_flush_one+0x266/0x350 fs/xfs/xfs_qm.c:1249
xfs_qm_dquot_walk+0x22a/0x4a0 fs/xfs/xfs_qm.c:86
xfs_qm_quotacheck+0x2f7/0x640 fs/xfs/xfs_qm.c:1335
xfs_qm_mount_quotas+0x328/0x610 fs/xfs/xfs_qm.c:1441
xfs_mountfs+0x162b/0x1ca0 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0x100c/0x1240 fs/xfs/xfs_super.c:1658
get_tree_bdev+0x3fe/0x620 fs/super.c:1294
vfs_get_tree+0x88/0x270 fs/super.c:1499
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f701c1d162a
RSP: 002b:00007f701a741f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00000000000095d1 RCX: 00007f701c1d162a
RDX: 0000000020000180 RSI: 0000000020009640 RDI: 00007f701a741fe0
RBP: 00007f701a742020 R08: 00007f701a742020 R09: 0000000000000090
R10: 0000000000000090 R11: 0000000000000202 R12: 0000000020000180
R13: 0000000020009640 R14: 00007f701a741fe0 R15: 0000000020000100
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/26:
#0: ffffffff8c91c2a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:4/1157:
2 locks held by getty/3270:
#0: ffff88814b1ae098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900020a32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
3 locks held by syz-executor.2/4867:
#0: ffff88802d01a0e0 (&type->s_umount_key#52/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff88802c940158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff88801efe1c78 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff88801efe1c78 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 26 Comm: khungtaskd Not tainted 5.15.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xf54/0xfa0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:109 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570
---
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.
syzbot
Jun 16, 2023, 7:38:01 AM6/16/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 471e639e59d1 Linux 5.15.117
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15abd17f280000
kernel config: https://syzkaller.appspot.com/x/.config?x=6390289bcc1381aa
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168eb59b280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/145b7f137d72/disk-471e639e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b5bd2fcb945c/vmlinux-471e639e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/794584032e0f/bzImage-471e639e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0f0ff30bf57f/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ae675...@syzkaller.appspotmail.com
INFO: task syz-executor199:5735 blocked for more than 143 seconds.
Not tainted 5.15.117-syzkaller #0
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
xfs_buf_delwri_pushbuf+0x2cf/0x4b0 fs/xfs/xfs_buf.c:2251
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
RSP: 002b:00007ffe28cf6138 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00646975756f6e2c RCX: 00007f8d14b9fc4a
RDX: 0000000020009700 RSI: 0000000020009740 RDI: 00007ffe28cf6150
RBP: 00007ffe28cf6150 R08: 00007ffe28cf6190 R09: 00000000000096c5
R10: 0000000002000000 R11: 0000000000000202 R12: 0000000000000004
R13: 000055555657a2c0 R14: 0000000002000000 R15: 00007ffe28cf6190
</TASK>
INFO: task syz-executor199:6256 blocked for more than 143 seconds.
Not tainted 5.15.117-syzkaller #0
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
xfs_buf_delwri_pushbuf+0x2cf/0x4b0 fs/xfs/xfs_buf.c:2251
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
RSP: 002b:00007ffe28cf6138 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00646975756f6e2c RCX: 00007f8d14b9fc4a
RDX: 0000000020009700 RSI: 0000000020009740 RDI: 00007ffe28cf6150
RBP: 00007ffe28cf6150 R08: 00007ffe28cf6190 R09: 00000000000096c5
R10: 0000000002000000 R11: 0000000000000202 R12: 0000000000000004
R13: 000055555657a2c0 R14: 0000000002000000 R15: 00007ffe28cf6190
#0: ffffffff8c91c5e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3255:
#0: ffff888024dba098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb52e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by syz-executor199/3557:
#0: ffff8880786780e0 (&type->s_umount_key#43){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:842
2 locks held by syz-executor199/3560:
#0: ffff8880775760e0 (&type->s_umount_key#43){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:842
1 lock held by syz-executor199/3561:
#0: ffff8880775060e0 (&type->s_umount_key#43){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
3 locks held by kworker/1:1/3624:
2 locks held by kworker/0:3/3628:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90002d4fd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
3 locks held by syz-executor199/5735:
#0: ffff8880249700e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff888074848158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff88807a385288 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff88807a385288 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
3 locks held by syz-executor199/6256:
#0: ffff8880770680e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff88801ea6a158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff88807a384be8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff88807a384be8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
2 locks held by kworker/0:5/10090:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc9000404fd20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
3 locks held by syz-executor199/10092:
#0: ffff88807f2ec0e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff88801e7d6158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff888071fe69b8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff888071fe69b8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.117-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Workqueue: events free_work
RIP: 0010:orc_find arch/x86/kernel/unwind_orc.c:178 [inline]
RIP: 0010:unwind_next_frame+0x27c/0x1fa0 arch/x86/kernel/unwind_orc.c:448
Code: 00 00 45 39 e0 0f 84 89 01 00 00 4a 8d 3c a5 40 8b ee 8d 45 29 e0 4a 8d 6c 87 fc 49 89 fc 48 39 fd 0f 83 77 02 00 00 49 29 fc <eb> 78 49 c7 c6 a0 6c 88 8a e9 7d 01 00 00 4c 89 ef e8 5e 06 1c 00
RSP: 0018:ffffc9000311f448 EFLAGS: 00000246
RAX: ffffffff8df11cd0 RBX: ffffffff8df11cd4 RCX: ffffffff8df11cd8
RDX: dffffc0000000000 RSI: ffffffff8e57d6f6 RDI: ffffffff8df11cd4
RBP: ffffffff8df11cd4 R08: 0000000000000007 R09: ffffc9000311f5b0
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffffffff812faf1a R14: ffffffff8df11cd8 R15: ffffc9000311f560
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe28cf4f78 CR3: 000000002358f000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
__unwind_start+0x59d/0x720 arch/x86/kernel/unwind_orc.c:704
unwind_start arch/x86/include/asm/unwind.h:60 [inline]
arch_stack_walk+0xdb/0x140 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x80 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd8/0x120 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]
slab_free_freelist_hook+0xdd/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kmem_cache_free+0x91/0x1f0 mm/slub.c:3515
merge_or_add_vmap_area mm/vmalloc.c:1142 [inline]
merge_or_add_vmap_area_augment mm/vmalloc.c:1161 [inline]
__purge_vmap_area_lazy+0x1365/0x1740 mm/vmalloc.c:1697
try_purge_vmap_area_lazy+0x34/0x50 mm/vmalloc.c:1723
free_unmap_vmap_area mm/vmalloc.c:1778 [inline]
remove_vm_area+0x1ae/0x1d0 mm/vmalloc.c:2517
vm_remove_mappings mm/vmalloc.c:2546 [inline]
__vunmap+0x325/0xa20 mm/vmalloc.c:2611
free_work+0x57/0x80 mm/vmalloc.c:95
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
---
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.
HEAD commit: 471e639e59d1 Linux 5.15.117
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15abd17f280000
kernel config: https://syzkaller.appspot.com/x/.config?x=6390289bcc1381aa
dashboard link: https://syzkaller.appspot.com/bug?extid=3ae67535b07c92aa02fd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11378ce3280000
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168eb59b280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/145b7f137d72/disk-471e639e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b5bd2fcb945c/vmlinux-471e639e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/794584032e0f/bzImage-471e639e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0f0ff30bf57f/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ae675...@syzkaller.appspotmail.com
Not tainted 5.15.117-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor199 state:D stack:23584 pid: 5735 ppid: 3559 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
xfs_buf_iowait+0xb4/0x400 fs/xfs/xfs_buf.c:1573
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
xfs_buf_delwri_pushbuf+0x2cf/0x4b0 fs/xfs/xfs_buf.c:2251
xfs_qm_flush_one+0x266/0x350 fs/xfs/xfs_qm.c:1249
xfs_qm_dquot_walk+0x22a/0x4a0 fs/xfs/xfs_qm.c:86
xfs_qm_quotacheck+0x2f7/0x640 fs/xfs/xfs_qm.c:1335
xfs_qm_mount_quotas+0x328/0x610 fs/xfs/xfs_qm.c:1441
xfs_mountfs+0x162b/0x1ca0 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0x100c/0x1240 fs/xfs/xfs_super.c:1658
get_tree_bdev+0x3fe/0x620 fs/super.c:1303
xfs_qm_dquot_walk+0x22a/0x4a0 fs/xfs/xfs_qm.c:86
xfs_qm_quotacheck+0x2f7/0x640 fs/xfs/xfs_qm.c:1335
xfs_qm_mount_quotas+0x328/0x610 fs/xfs/xfs_qm.c:1441
xfs_mountfs+0x162b/0x1ca0 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0x100c/0x1240 fs/xfs/xfs_super.c:1658
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8d14b9fc4a
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RSP: 002b:00007ffe28cf6138 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00646975756f6e2c RCX: 00007f8d14b9fc4a
RDX: 0000000020009700 RSI: 0000000020009740 RDI: 00007ffe28cf6150
RBP: 00007ffe28cf6150 R08: 00007ffe28cf6190 R09: 00000000000096c5
R10: 0000000002000000 R11: 0000000000000202 R12: 0000000000000004
R13: 000055555657a2c0 R14: 0000000002000000 R15: 00007ffe28cf6190
</TASK>
INFO: task syz-executor199:6256 blocked for more than 143 seconds.
Not tainted 5.15.117-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor199 state:D stack:23584 pid: 6256 ppid: 3562 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
xfs_buf_iowait+0xb4/0x400 fs/xfs/xfs_buf.c:1573
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
xfs_buf_delwri_pushbuf+0x2cf/0x4b0 fs/xfs/xfs_buf.c:2251
xfs_qm_flush_one+0x266/0x350 fs/xfs/xfs_qm.c:1249
xfs_qm_dquot_walk+0x22a/0x4a0 fs/xfs/xfs_qm.c:86
xfs_qm_quotacheck+0x2f7/0x640 fs/xfs/xfs_qm.c:1335
xfs_qm_mount_quotas+0x328/0x610 fs/xfs/xfs_qm.c:1441
xfs_mountfs+0x162b/0x1ca0 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0x100c/0x1240 fs/xfs/xfs_super.c:1658
get_tree_bdev+0x3fe/0x620 fs/super.c:1303
xfs_qm_dquot_walk+0x22a/0x4a0 fs/xfs/xfs_qm.c:86
xfs_qm_quotacheck+0x2f7/0x640 fs/xfs/xfs_qm.c:1335
xfs_qm_mount_quotas+0x328/0x610 fs/xfs/xfs_qm.c:1441
xfs_mountfs+0x162b/0x1ca0 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0x100c/0x1240 fs/xfs/xfs_super.c:1658
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8d14b9fc4a
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RSP: 002b:00007ffe28cf6138 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00646975756f6e2c RCX: 00007f8d14b9fc4a
RDX: 0000000020009700 RSI: 0000000020009740 RDI: 00007ffe28cf6150
RBP: 00007ffe28cf6150 R08: 00007ffe28cf6190 R09: 00000000000096c5
R10: 0000000002000000 R11: 0000000000000202 R12: 0000000000000004
R13: 000055555657a2c0 R14: 0000000002000000 R15: 00007ffe28cf6190
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
Showing all locks held in the system:
#0: ffffffff8c91c5e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3255:
#0: ffff888024dba098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb52e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by syz-executor199/3557:
#0: ffff8880786780e0 (&type->s_umount_key#43){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:842
2 locks held by syz-executor199/3560:
#0: ffff8880775760e0 (&type->s_umount_key#43){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c920b28 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:842
1 lock held by syz-executor199/3561:
#0: ffff8880775060e0 (&type->s_umount_key#43){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
3 locks held by kworker/1:1/3624:
2 locks held by kworker/0:3/3628:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90002d4fd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
3 locks held by syz-executor199/5735:
#0: ffff8880249700e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff888074848158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff88807a385288 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff88807a385288 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
3 locks held by syz-executor199/6256:
#0: ffff8880770680e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff88801ea6a158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff88807a384be8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff88807a384be8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
2 locks held by kworker/0:5/10090:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc9000404fd20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
3 locks held by syz-executor199/10092:
#0: ffff88807f2ec0e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229
#1: ffff88801e7d6158 (&qinf->qi_tree_lock){+.+.}-{3:3}, at: xfs_qm_dquot_walk+0x132/0x4a0 fs/xfs/xfs_qm.c:73
#2: ffff888071fe69b8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_dqlock fs/xfs/xfs_dquot.h:133 [inline]
#2: ffff888071fe69b8 (&dqp->q_qlock){+.+.}-{3:3}, at: xfs_qm_flush_one+0xca/0x350 fs/xfs/xfs_qm.c:1225
=============================================
NMI backtrace for cpu 0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3624 Comm: kworker/1:1 Not tainted 5.15.117-syzkaller #0
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Workqueue: events free_work
RIP: 0010:orc_find arch/x86/kernel/unwind_orc.c:178 [inline]
RIP: 0010:unwind_next_frame+0x27c/0x1fa0 arch/x86/kernel/unwind_orc.c:448
Code: 00 00 45 39 e0 0f 84 89 01 00 00 4a 8d 3c a5 40 8b ee 8d 45 29 e0 4a 8d 6c 87 fc 49 89 fc 48 39 fd 0f 83 77 02 00 00 49 29 fc <eb> 78 49 c7 c6 a0 6c 88 8a e9 7d 01 00 00 4c 89 ef e8 5e 06 1c 00
RSP: 0018:ffffc9000311f448 EFLAGS: 00000246
RAX: ffffffff8df11cd0 RBX: ffffffff8df11cd4 RCX: ffffffff8df11cd8
RDX: dffffc0000000000 RSI: ffffffff8e57d6f6 RDI: ffffffff8df11cd4
RBP: ffffffff8df11cd4 R08: 0000000000000007 R09: ffffc9000311f5b0
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffffffff812faf1a R14: ffffffff8df11cd8 R15: ffffc9000311f560
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe28cf4f78 CR3: 000000002358f000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
__unwind_start+0x59d/0x720 arch/x86/kernel/unwind_orc.c:704
unwind_start arch/x86/include/asm/unwind.h:60 [inline]
arch_stack_walk+0xdb/0x140 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x80 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd8/0x120 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]
slab_free_freelist_hook+0xdd/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kmem_cache_free+0x91/0x1f0 mm/slub.c:3515
merge_or_add_vmap_area mm/vmalloc.c:1142 [inline]
merge_or_add_vmap_area_augment mm/vmalloc.c:1161 [inline]
__purge_vmap_area_lazy+0x1365/0x1740 mm/vmalloc.c:1697
try_purge_vmap_area_lazy+0x34/0x50 mm/vmalloc.c:1723
free_unmap_vmap_area mm/vmalloc.c:1778 [inline]
remove_vm_area+0x1ae/0x1d0 mm/vmalloc.c:2517
vm_remove_mappings mm/vmalloc.c:2546 [inline]
__vunmap+0x325/0xa20 mm/vmalloc.c:2611
free_work+0x57/0x80 mm/vmalloc.c:95
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
---
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
Dec 4, 2023, 10:56:06 AM12/4/23
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 8d0baec78e8a7abe03b449820507c9777dae7f7b
Author: Darrick J. Wong <djw...@kernel.org>
Date: Thu Nov 16 02:28:26 2023 +0000
xfs: fix intermittent hang during quotacheck
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10966530e80000
start commit: 35ecaa3632bf Linux 5.15.132
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=7e1620fbf0341078
dashboard link: https://syzkaller.appspot.com/bug?extid=3ae67535b07c92aa02fd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144340d4680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117ddf9c680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfs: fix intermittent hang during quotacheck
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit 8d0baec78e8a7abe03b449820507c9777dae7f7b
Author: Darrick J. Wong <djw...@kernel.org>
Date: Thu Nov 16 02:28:26 2023 +0000
xfs: fix intermittent hang during quotacheck
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10966530e80000
start commit: 35ecaa3632bf Linux 5.15.132
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=7e1620fbf0341078
dashboard link: https://syzkaller.appspot.com/bug?extid=3ae67535b07c92aa02fd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144340d4680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117ddf9c680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfs: fix intermittent hang during quotacheck
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages