[v6.1] INFO: task hung in f2fs_issue_checkpoint
0 views
Skip to first unread message
syzbot
Jul 6, 2024, 1:28:22 AM (yesterday) Jul 6
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 7753af06eebf Linux 6.1.97
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15929969980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8598d0ff7c47577b
dashboard link: https://syzkaller.appspot.com/bug?extid=ae3eae1f64c08f12e790
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ba92bc446d9/disk-7753af06.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/96a956b7234b/vmlinux-7753af06.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb054c41985f/bzImage-7753af06.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ae3eae...@syzkaller.appspotmail.com
INFO: task syz.1.142:4257 blocked for more than 144 seconds.
Not tainted 6.1.97-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.142 state:D stack:24248 pid:4257 ppid:3551 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
f2fs_issue_checkpoint+0x2d2/0x4d0 fs/f2fs/checkpoint.c:1864
f2fs_create+0x862/0xa10 fs/f2fs/namei.c:377
lookup_open fs/namei.c:3484 [inline]
open_last_lookups fs/namei.c:3552 [inline]
path_openat+0x12f1/0x2e60 fs/namei.c:3782
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f3320575bd9
RSP: 002b:00007f3321372048 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f3320704038 RCX: 00007f3320575bd9
RDX: 00000000000026e1 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00007f33205e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f3320704038 R15: 00007fffffc06738
</TASK>
INFO: task syz.1.142:4263 blocked for more than 146 seconds.
Not tainted 6.1.97-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.142 state:D stack:26384 pid:4263 ppid:3551 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
inode_lock include/linux/fs.h:758 [inline]
process_measurement+0x446/0x21b0 security/integrity/ima/ima_main.c:242
ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:534
do_open fs/namei.c:3630 [inline]
path_openat+0x2687/0x2e60 fs/namei.c:3785
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f3320575bd9
RSP: 002b:00007f3321330048 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f33207041e8 RCX: 00007f3320575bd9
RDX: 0000000000183341 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00007f33205e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f33207041e8 R15: 00007fffffc06738
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12aed0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b6d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0:
ffffffff8d12ad00 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
ffffffff8d12ad00 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
ffffffff8d12ad00 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3305:
#0: ffff888028bf7098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:5/3620:
#0: ffff888014a44938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000440fd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888064ca00e0 (&type->s_umount_key#68){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff8880544bd140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#3: ffff8880544bd140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4fb/0x6c0 fs/f2fs/segment.c:428
2 locks held by kworker/u4:6/3631:
4 locks held by kworker/u4:10/3778:
#0: ffff888014a44938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc900048b7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888077c6e0e0 (&type->s_umount_key#68){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#3: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4fb/0x6c0 fs/f2fs/segment.c:428
4 locks held by kworker/u4:11/3809:
#0: ffff888014a44938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc900049b7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff88807c84a0e0 (&type->s_umount_key#68){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#3: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4fb/0x6c0 fs/f2fs/segment.c:428
3 locks held by syz.1.142/4257:
#0: ffff888077c6e460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a1424d0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a1424d0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff88805a1424d0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: path_openat+0x7b6/0x2e60 fs/namei.c:3782
#2: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#2: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_issue_checkpoint+0x2d2/0x4d0 fs/f2fs/checkpoint.c:1864
4 locks held by syz.1.142/4261:
2 locks held by syz.1.142/4263:
#0: ffff888077c6e460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a27a4d0 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a27a4d0 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: process_measurement+0x446/0x21b0 security/integrity/ima/ima_main.c:242
2 locks held by kworker/0:9/4837:
#0: ffff888012472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90004937d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
4 locks held by syz.3.306/4864:
2 locks held by syz.3.306/4865:
#0: ffff88807c84a460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a279310 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a279310 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: process_measurement+0x446/0x21b0 security/integrity/ima/ima_main.c:242
3 locks held by syz.3.306/4867:
#0: ffff88807c84a460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a278a30 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a278a30 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff88805a278a30 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: path_openat+0x7b6/0x2e60 fs/namei.c:3782
#2: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#2: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_issue_checkpoint+0x2d2/0x4d0 fs/f2fs/checkpoint.c:1864
1 lock held by syz-executor/4935:
#0: ffffffff8d1301c0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x5f0 kernel/rcu/tree.c:4018
5 locks held by syz.2.435/5295:
2 locks held by syz-executor/5632:
#0: ffffffff8e299b68 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e299b68 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7c1/0xff0 net/core/rtnetlink.c:6118
#1: ffffffff8d1302f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#1: ffffffff8d1302f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x4f0/0x930 kernel/rcu/tree_exp.h:962
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5295 Comm: syz.2.435 Not tainted 6.1.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:down_read+0x842/0xa30 kernel/locking/rwsem.c:1523
Code: d5 a0 f9 bf 01 00 00 00 e8 ab f1 c9 f6 65 8b 05 0c fe 6d 75 85 c0 74 5a 48 c7 44 24 60 0e 36 e0 45 43 c7 44 25 00 00 00 00 00 <4b> c7 44 25 0a 00 00 00 00 66 43 c7 44 25 12 00 00 65 48 8b 04 25
RSP: 0018:ffffc9001215e9c0 EFLAGS: 00000286
RAX: 0000000080000000 RBX: ffff888026b1b060 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000008 RDI: 0000000000000001
RBP: ffffc9001215eb10 R08: dffffc0000000000 R09: ffffed1004d6360d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff9200242bd44
R13: dffffc0000000000 R14: ffff888027500001 R15: 1ffff11004d6360c
FS: 00007fe22a4896c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f497b082440 CR3: 0000000077037000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
check_valid_map fs/f2fs/gc.c:988 [inline]
gc_data_segment fs/f2fs/gc.c:1540 [inline]
do_garbage_collect+0x21ed/0x81f0 fs/f2fs/gc.c:1774
f2fs_gc+0x1169/0x32a0 fs/f2fs/gc.c:1873
f2fs_balance_fs+0x506/0x6c0 fs/f2fs/segment.c:429
f2fs_map_blocks+0x2871/0x3ab0 fs/f2fs/data.c:1705
expand_inode_data+0x56d/0xaf0 fs/f2fs/file.c:1749
f2fs_fallocate+0x44a/0x9f0 fs/f2fs/file.c:1846
vfs_fallocate+0x547/0x6b0 fs/open.c:323
do_vfs_ioctl+0x222c/0x2a90 fs/ioctl.c:849
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe229775bd9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe22a489048 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fe229903f60 RCX: 00007fe229775bd9
RDX: 00000000200000c0 RSI: 0000000040305828 RDI: 0000000000000004
RBP: 00007fe2297e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fe229903f60 R15: 00007ffc645539e8
</TASK>
---
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 found the following issue on:
HEAD commit: 7753af06eebf Linux 6.1.97
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15929969980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8598d0ff7c47577b
dashboard link: https://syzkaller.appspot.com/bug?extid=ae3eae1f64c08f12e790
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ba92bc446d9/disk-7753af06.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/96a956b7234b/vmlinux-7753af06.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb054c41985f/bzImage-7753af06.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ae3eae...@syzkaller.appspotmail.com
INFO: task syz.1.142:4257 blocked for more than 144 seconds.
Not tainted 6.1.97-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.142 state:D stack:24248 pid:4257 ppid:3551 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
f2fs_issue_checkpoint+0x2d2/0x4d0 fs/f2fs/checkpoint.c:1864
f2fs_create+0x862/0xa10 fs/f2fs/namei.c:377
lookup_open fs/namei.c:3484 [inline]
open_last_lookups fs/namei.c:3552 [inline]
path_openat+0x12f1/0x2e60 fs/namei.c:3782
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f3320575bd9
RSP: 002b:00007f3321372048 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f3320704038 RCX: 00007f3320575bd9
RDX: 00000000000026e1 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00007f33205e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f3320704038 R15: 00007fffffc06738
</TASK>
INFO: task syz.1.142:4263 blocked for more than 146 seconds.
Not tainted 6.1.97-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.142 state:D stack:26384 pid:4263 ppid:3551 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
inode_lock include/linux/fs.h:758 [inline]
process_measurement+0x446/0x21b0 security/integrity/ima/ima_main.c:242
ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:534
do_open fs/namei.c:3630 [inline]
path_openat+0x2687/0x2e60 fs/namei.c:3785
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f3320575bd9
RSP: 002b:00007f3321330048 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f33207041e8 RCX: 00007f3320575bd9
RDX: 0000000000183341 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00007f33205e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f33207041e8 R15: 00007fffffc06738
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12aed0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b6d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0:
ffffffff8d12ad00 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
ffffffff8d12ad00 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
ffffffff8d12ad00 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3305:
#0: ffff888028bf7098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:5/3620:
#0: ffff888014a44938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000440fd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888064ca00e0 (&type->s_umount_key#68){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff8880544bd140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#3: ffff8880544bd140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4fb/0x6c0 fs/f2fs/segment.c:428
2 locks held by kworker/u4:6/3631:
4 locks held by kworker/u4:10/3778:
#0: ffff888014a44938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc900048b7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888077c6e0e0 (&type->s_umount_key#68){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#3: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4fb/0x6c0 fs/f2fs/segment.c:428
4 locks held by kworker/u4:11/3809:
#0: ffff888014a44938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc900049b7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff88807c84a0e0 (&type->s_umount_key#68){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#3: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4fb/0x6c0 fs/f2fs/segment.c:428
3 locks held by syz.1.142/4257:
#0: ffff888077c6e460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a1424d0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a1424d0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff88805a1424d0 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: path_openat+0x7b6/0x2e60 fs/namei.c:3782
#2: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#2: ffff88807bfe5140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_issue_checkpoint+0x2d2/0x4d0 fs/f2fs/checkpoint.c:1864
4 locks held by syz.1.142/4261:
2 locks held by syz.1.142/4263:
#0: ffff888077c6e460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a27a4d0 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a27a4d0 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: process_measurement+0x446/0x21b0 security/integrity/ima/ima_main.c:242
2 locks held by kworker/0:9/4837:
#0: ffff888012472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90004937d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
4 locks held by syz.3.306/4864:
2 locks held by syz.3.306/4865:
#0: ffff88807c84a460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a279310 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a279310 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: process_measurement+0x446/0x21b0 security/integrity/ima/ima_main.c:242
3 locks held by syz.3.306/4867:
#0: ffff88807c84a460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88805a278a30 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff88805a278a30 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff88805a278a30 (&type->i_mutex_dir_key#11){++++}-{3:3}, at: path_openat+0x7b6/0x2e60 fs/namei.c:3782
#2: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2176 [inline]
#2: ffff888060bc1140 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_issue_checkpoint+0x2d2/0x4d0 fs/f2fs/checkpoint.c:1864
1 lock held by syz-executor/4935:
#0: ffffffff8d1301c0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x5f0 kernel/rcu/tree.c:4018
5 locks held by syz.2.435/5295:
2 locks held by syz-executor/5632:
#0: ffffffff8e299b68 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e299b68 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7c1/0xff0 net/core/rtnetlink.c:6118
#1: ffffffff8d1302f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#1: ffffffff8d1302f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x4f0/0x930 kernel/rcu/tree_exp.h:962
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5295 Comm: syz.2.435 Not tainted 6.1.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:down_read+0x842/0xa30 kernel/locking/rwsem.c:1523
Code: d5 a0 f9 bf 01 00 00 00 e8 ab f1 c9 f6 65 8b 05 0c fe 6d 75 85 c0 74 5a 48 c7 44 24 60 0e 36 e0 45 43 c7 44 25 00 00 00 00 00 <4b> c7 44 25 0a 00 00 00 00 66 43 c7 44 25 12 00 00 65 48 8b 04 25
RSP: 0018:ffffc9001215e9c0 EFLAGS: 00000286
RAX: 0000000080000000 RBX: ffff888026b1b060 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000008 RDI: 0000000000000001
RBP: ffffc9001215eb10 R08: dffffc0000000000 R09: ffffed1004d6360d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff9200242bd44
R13: dffffc0000000000 R14: ffff888027500001 R15: 1ffff11004d6360c
FS: 00007fe22a4896c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f497b082440 CR3: 0000000077037000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
check_valid_map fs/f2fs/gc.c:988 [inline]
gc_data_segment fs/f2fs/gc.c:1540 [inline]
do_garbage_collect+0x21ed/0x81f0 fs/f2fs/gc.c:1774
f2fs_gc+0x1169/0x32a0 fs/f2fs/gc.c:1873
f2fs_balance_fs+0x506/0x6c0 fs/f2fs/segment.c:429
f2fs_map_blocks+0x2871/0x3ab0 fs/f2fs/data.c:1705
expand_inode_data+0x56d/0xaf0 fs/f2fs/file.c:1749
f2fs_fallocate+0x44a/0x9f0 fs/f2fs/file.c:1846
vfs_fallocate+0x547/0x6b0 fs/open.c:323
do_vfs_ioctl+0x222c/0x2a90 fs/ioctl.c:849
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe229775bd9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe22a489048 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fe229903f60 RCX: 00007fe229775bd9
RDX: 00000000200000c0 RSI: 0000000040305828 RDI: 0000000000000004
RBP: 00007fe2297e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fe229903f60 R15: 00007ffc645539e8
</TASK>
---
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
Reply all
Reply to author
Forward
0 new messages