[v5.15] INFO: task hung in xlog_grant_head_check
10 views
Skip to first unread message
syzbot
Mar 25, 2023, 3:23:35 AM3/25/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d614f5c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e597b110d58e7b4
dashboard link: https://syzkaller.appspot.com/bug?extid=df79f3637753ffa39784
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/76798ca1c9b6/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b608633c8f5/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8836fafb618b/Image-11547239.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df79f3...@syzkaller.appspotmail.com
INFO: task syz-executor.1:12086 blocked for more than 143 seconds.
Not tainted 5.15.104-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack: 0 pid:12086 ppid: 4101 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6369
schedule+0x11c/0x1c8 kernel/sched/core.c:6452
xlog_grant_head_wait+0x390/0xa88 fs/xfs/xfs_log.c:256
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x384/0xc1c fs/xfs/xfs_log.c:464
xfs_trans_reserve+0x1e8/0x5a4 fs/xfs/xfs_trans.c:197
xfs_trans_alloc+0x4c4/0xaa4 fs/xfs/xfs_trans.c:288
xfs_qm_qino_alloc+0x348/0x864 fs/xfs/xfs_qm.c:779
xfs_qm_init_quotainos+0x500/0x72c fs/xfs/xfs_qm.c:1544
xfs_qm_init_quotainfo+0x9c/0x8bc fs/xfs/xfs_qm.c:644
xfs_qm_mount_quotas+0x90/0x578 fs/xfs/xfs_qm.c:1428
xfs_mountfs+0x11e4/0x1778 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0xd64/0xf60 fs/xfs/xfs_super.c:1658
get_tree_bdev+0x360/0x54c fs/super.c:1294
xfs_fs_get_tree+0x28/0x38 fs/xfs/xfs_super.c:1705
vfs_get_tree+0x90/0x274 fs/super.c:1499
do_new_mount+0x25c/0x8c8 fs/namespace.c:2994
path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
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: ffff800014a91660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3733:
#0: ffff0000d2ac5098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a0ae2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
1 lock held by syz-executor.4/4100:
2 locks held by kworker/1:18/19952:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2279
#1: ffff80001c9a7c00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2281
2 locks held by kworker/u4:11/21504:
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1325 [inline]
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1620 [inline]
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e38 kernel/sched/core.c:6283
#1: ffff0001b481fc48 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x438/0x66c kernel/sched/psi.c:891
2 locks held by kworker/0:8/30987:
#0: ffff0000c0021d38 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2279
#1: ffff800026397c00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2281
2 locks held by syz-executor.1/12086:
#0: ffff0000d00740e0 (&type->s_umount_key#76/1){+.+.}-{3:3}, at: alloc_super+0x1b8/0x844 fs/super.c:229
#1: ffff0000d0074650 (sb_internal#3){.+.+}-{0:0}, at: xfs_qm_qino_alloc+0x348/0x864 fs/xfs/xfs_qm.c:779
1 lock held by udevd/12111:
2 locks held by udevd/12120:
#0: ffff0000cba96918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cb9f3468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1348
2 locks held by udevd/12126:
#0: ffff0000cb9d9118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cb9c2468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1348
1 lock held by syz-executor.3/15904:
#0: ffff0000cba96918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x12c/0x89c block/bdev.c:817
2 locks held by syz-executor.5/15913:
#0: ffff00011aaf03f0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff00011aaf03f0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: lock_mount+0x68/0x26c fs/namespace.c:2248
#1: ffff800014a95be8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffff800014a95be8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x660 kernel/rcu/tree_exp.h:840
1 lock held by syz-executor.0/15915:
#0: ffff0000cb9d9118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x12c/0x89c block/bdev.c:817
1 lock held by syz-executor.4/15925:
=============================================
---
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: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d614f5c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e597b110d58e7b4
dashboard link: https://syzkaller.appspot.com/bug?extid=df79f3637753ffa39784
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/76798ca1c9b6/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b608633c8f5/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8836fafb618b/Image-11547239.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df79f3...@syzkaller.appspotmail.com
INFO: task syz-executor.1:12086 blocked for more than 143 seconds.
Not tainted 5.15.104-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack: 0 pid:12086 ppid: 4101 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6369
schedule+0x11c/0x1c8 kernel/sched/core.c:6452
xlog_grant_head_wait+0x390/0xa88 fs/xfs/xfs_log.c:256
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x384/0xc1c fs/xfs/xfs_log.c:464
xfs_trans_reserve+0x1e8/0x5a4 fs/xfs/xfs_trans.c:197
xfs_trans_alloc+0x4c4/0xaa4 fs/xfs/xfs_trans.c:288
xfs_qm_qino_alloc+0x348/0x864 fs/xfs/xfs_qm.c:779
xfs_qm_init_quotainos+0x500/0x72c fs/xfs/xfs_qm.c:1544
xfs_qm_init_quotainfo+0x9c/0x8bc fs/xfs/xfs_qm.c:644
xfs_qm_mount_quotas+0x90/0x578 fs/xfs/xfs_qm.c:1428
xfs_mountfs+0x11e4/0x1778 fs/xfs/xfs_mount.c:904
xfs_fs_fill_super+0xd64/0xf60 fs/xfs/xfs_super.c:1658
get_tree_bdev+0x360/0x54c fs/super.c:1294
xfs_fs_get_tree+0x28/0x38 fs/xfs/xfs_super.c:1705
vfs_get_tree+0x90/0x274 fs/super.c:1499
do_new_mount+0x25c/0x8c8 fs/namespace.c:2994
path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
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: ffff800014a91660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3733:
#0: ffff0000d2ac5098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a0ae2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
1 lock held by syz-executor.4/4100:
2 locks held by kworker/1:18/19952:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2279
#1: ffff80001c9a7c00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2281
2 locks held by kworker/u4:11/21504:
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1325 [inline]
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1620 [inline]
#0: ffff0001b4831d18 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e38 kernel/sched/core.c:6283
#1: ffff0001b481fc48 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x438/0x66c kernel/sched/psi.c:891
2 locks held by kworker/0:8/30987:
#0: ffff0000c0021d38 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2279
#1: ffff800026397c00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2281
2 locks held by syz-executor.1/12086:
#0: ffff0000d00740e0 (&type->s_umount_key#76/1){+.+.}-{3:3}, at: alloc_super+0x1b8/0x844 fs/super.c:229
#1: ffff0000d0074650 (sb_internal#3){.+.+}-{0:0}, at: xfs_qm_qino_alloc+0x348/0x864 fs/xfs/xfs_qm.c:779
1 lock held by udevd/12111:
2 locks held by udevd/12120:
#0: ffff0000cba96918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cb9f3468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1348
2 locks held by udevd/12126:
#0: ffff0000cb9d9118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cb9c2468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1348
1 lock held by syz-executor.3/15904:
#0: ffff0000cba96918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x12c/0x89c block/bdev.c:817
2 locks held by syz-executor.5/15913:
#0: ffff00011aaf03f0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff00011aaf03f0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: lock_mount+0x68/0x26c fs/namespace.c:2248
#1: ffff800014a95be8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffff800014a95be8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x660 kernel/rcu/tree_exp.h:840
1 lock held by syz-executor.0/15915:
#0: ffff0000cb9d9118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x12c/0x89c block/bdev.c:817
1 lock held by syz-executor.4/15925:
=============================================
---
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
Apr 2, 2023, 3:36:42 PM4/2/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3b29299e5f60 Linux 6.1.22
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12315725c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=bbb9a1f6f7f5a1d9
dashboard link: https://syzkaller.appspot.com/bug?extid=eac983dc519d85988637
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2affbd06cbfd/disk-3b29299e.raw.xz
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/8b22d1baf827/vmlinux-3b29299e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d5e3891c88bf/Image-3b29299e.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
INFO: task syz-executor.3:7715 blocked for more than 143 seconds.
Not tainted 6.1.22-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:0 pid:7715 ppid:4352 flags:0x00000001
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
xlog_grant_head_wait+0x3bc/0xbac fs/xfs/xfs_log.c:307
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x3a8/0xd20 fs/xfs/xfs_log.c:486
xfs_trans_reserve+0x1f4/0x5e0 fs/xfs/xfs_trans.c:194
xfs_trans_alloc+0x440/0x9d0 fs/xfs/xfs_trans.c:283
xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
xfs_create+0x5a0/0xff4 fs/xfs/xfs_inode.c:1002
xfs_generic_create+0x3c8/0xb10 fs/xfs/xfs_iops.c:199
xfs_vn_mkdir+0x44/0x58 fs/xfs/xfs_iops.c:285
vfs_mkdir+0x334/0x4e4 fs/namei.c:4036
do_mkdirat+0x20c/0x610 fs/namei.c:4061
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4074
__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:581
Showing all locks held in the system:
#0: ffff800015754a30 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffff800015755230 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffff800015754860 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3989:
#0: ffff0000d3974098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001ca002f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
3 locks held by syz-executor.3/7715:
#0: ffff0001298ca460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e02a48f8 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
#1: ffff0000e02a48f8 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: filename_create+0x200/0x464 fs/namei.c:3807
#2: ffff0001298ca650 (sb_internal#2){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
3 locks held by syz-executor.4/7788:
#0: ffff000142d16460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e02a12b8 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
#1: ffff0000e02a12b8 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3}, at: filename_create+0x200/0x464 fs/namei.c:3807
#2: ffff000142d16650 (sb_internal#2){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
1 lock held by syz-executor.1/8972:
2 locks held by syz-executor.5/8998:
syzbot
May 21, 2023, 7:49:12 AM5/21/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: fa74641fb6b9 Linux 6.1.29
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12746ac5280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7454aa89ac475d7b
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12eccfe9280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/53e4da6b145c/disk-fa74641f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adeb1a2cfa86/vmlinux-fa74641f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c976f1155d08/Image-fa74641f.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/798b1fcb175a/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eac983...@syzkaller.appspotmail.com
INFO: task syz-executor664:4253 blocked for more than 143 seconds.
Not tainted 6.1.29-syzkaller #0
lookup_open fs/namei.c:3413 [inline]
open_last_lookups fs/namei.c:3481 [inline]
path_openat+0xeac/0x2548 fs/namei.c:3711
do_filp_open+0x1bc/0x3cc fs/namei.c:3741
do_sys_openat2+0x128/0x3d8 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_openat fs/open.c:1342 [inline]
__se_sys_openat fs/open.c:1337 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1337
2 locks held by getty/3975:
#0: ffff0000d5f7e098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001ca402f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
3 locks held by syz-executor664/4253:
#0: ffff0000d47d0460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e2440338 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#1: ffff0000e2440338 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3478 [inline]
#1: ffff0000e2440338 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3711
#2: ffff0000d47d0650 (sb_internal#2){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
=============================================
---
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: fa74641fb6b9 Linux 6.1.29
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12746ac5280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7454aa89ac475d7b
dashboard link: https://syzkaller.appspot.com/bug?extid=eac983dc519d85988637
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127cba29280000
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12eccfe9280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/53e4da6b145c/disk-fa74641f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adeb1a2cfa86/vmlinux-fa74641f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c976f1155d08/Image-fa74641f.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/798b1fcb175a/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eac983...@syzkaller.appspotmail.com
Not tainted 6.1.29-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor664 state:D stack:0 pid:4253 ppid:4252 flags:0x00000009
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
xlog_grant_head_wait+0x3bc/0xbac fs/xfs/xfs_log.c:307
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x3a8/0xd20 fs/xfs/xfs_log.c:486
xfs_trans_reserve+0x1f4/0x5e0 fs/xfs/xfs_trans.c:194
xfs_trans_alloc+0x440/0x9d0 fs/xfs/xfs_trans.c:283
xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
xfs_create+0x5a0/0xff4 fs/xfs/xfs_inode.c:1002
xfs_generic_create+0x3c8/0xb10 fs/xfs/xfs_iops.c:199
xfs_vn_create+0x44/0x58 fs/xfs/xfs_iops.c:275
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
xlog_grant_head_wait+0x3bc/0xbac fs/xfs/xfs_log.c:307
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x3a8/0xd20 fs/xfs/xfs_log.c:486
xfs_trans_reserve+0x1f4/0x5e0 fs/xfs/xfs_trans.c:194
xfs_trans_alloc+0x440/0x9d0 fs/xfs/xfs_trans.c:283
xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
xfs_create+0x5a0/0xff4 fs/xfs/xfs_inode.c:1002
xfs_generic_create+0x3c8/0xb10 fs/xfs/xfs_iops.c:199
lookup_open fs/namei.c:3413 [inline]
open_last_lookups fs/namei.c:3481 [inline]
path_openat+0xeac/0x2548 fs/namei.c:3711
do_filp_open+0x1bc/0x3cc fs/namei.c:3741
do_sys_openat2+0x128/0x3d8 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_openat fs/open.c:1342 [inline]
__se_sys_openat fs/open.c:1337 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1337
__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:581
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015774ef0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
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:581
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
1 lock held by rcu_tasks_trace/13:
#0: ffff8000157756f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffff800015774d20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3975:
#0: ffff0000d5f7e098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001ca402f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
3 locks held by syz-executor664/4253:
#0: ffff0000d47d0460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e2440338 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#1: ffff0000e2440338 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3478 [inline]
#1: ffff0000e2440338 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: path_openat+0x5ec/0x2548 fs/namei.c:3711
#2: ffff0000d47d0650 (sb_internal#2){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1246
=============================================
---
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
May 21, 2023, 8:51:10 AM5/21/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1247ab2e280000
kernel config: https://syzkaller.appspot.com/x/.config?x=508f7a387ef8f82b
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1608dac5280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8ab2bd416bb/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c358e3d58bb2/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c82319bbaeb8/Image-9d6bde85.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/98bf806c3c26/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df79f3...@syzkaller.appspotmail.com
INFO: task syz-executor290:3998 blocked for more than 143 seconds.
Not tainted 5.15.112-syzkaller #0
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
xfs_create+0x578/0xfec fs/xfs/xfs_inode.c:1018
xfs_generic_create+0x390/0xb70 fs/xfs/xfs_iops.c:197
xfs_vn_create+0x44/0x58 fs/xfs/xfs_iops.c:275
lookup_open fs/namei.c:3392 [inline]
open_last_lookups fs/namei.c:3462 [inline]
path_openat+0xec0/0x26f0 fs/namei.c:3669
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
2 locks held by getty/3719:
#0: ffff0000d04dd098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a27b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by syz-executor290/3998:
#0: ffff0000ca2a8460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000e04b8300 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff0000e04b8300 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
#1: ffff0000e04b8300 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: path_openat+0x63c/0x26f0 fs/namei.c:3669
#2: ffff0000ca2a8650 (sb_internal#2){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1102
HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1247ab2e280000
kernel config: https://syzkaller.appspot.com/x/.config?x=508f7a387ef8f82b
dashboard link: https://syzkaller.appspot.com/bug?extid=df79f3637753ffa39784
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1249a6de280000
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1608dac5280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8ab2bd416bb/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c358e3d58bb2/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c82319bbaeb8/Image-9d6bde85.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/98bf806c3c26/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df79f3...@syzkaller.appspotmail.com
Not tainted 5.15.112-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor290 state:D stack: 0 pid: 3998 ppid: 3997 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
xlog_grant_head_wait+0x390/0xa88 fs/xfs/xfs_log.c:256
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x384/0xc1c fs/xfs/xfs_log.c:464
xfs_trans_reserve+0x1e8/0x5a4 fs/xfs/xfs_trans.c:197
xfs_trans_alloc+0x4c4/0xaa4 fs/xfs/xfs_trans.c:288
xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1102
xlog_grant_head_check+0x218/0x3d8
xfs_log_reserve+0x384/0xc1c fs/xfs/xfs_log.c:464
xfs_trans_reserve+0x1e8/0x5a4 fs/xfs/xfs_trans.c:197
xfs_trans_alloc+0x4c4/0xaa4 fs/xfs/xfs_trans.c:288
xfs_create+0x578/0xfec fs/xfs/xfs_inode.c:1018
xfs_generic_create+0x390/0xb70 fs/xfs/xfs_iops.c:197
xfs_vn_create+0x44/0x58 fs/xfs/xfs_iops.c:275
lookup_open fs/namei.c:3392 [inline]
open_last_lookups fs/namei.c:3462 [inline]
path_openat+0xec0/0x26f0 fs/namei.c:3669
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
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: ffff800014aa19e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
1 lock held by khungtaskd/27:
2 locks held by getty/3719:
#0: ffff0000d04dd098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a27b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by syz-executor290/3998:
#0: ffff0000ca2a8460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000e04b8300 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff0000e04b8300 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
#1: ffff0000e04b8300 (&inode->i_sb->s_type->i_mutex_dir_key){+.+.}-{3:3}, at: path_openat+0x63c/0x26f0 fs/namei.c:3669
#2: ffff0000ca2a8650 (sb_internal#2){.+.+}-{0:0}, at: xfs_trans_alloc_icreate+0xc8/0x290 fs/xfs/xfs_trans.c:1102
Reply all
Reply to author
Forward
0 new messages