From: syzbot <syzbot+73d18077a2323a1fdb5e@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [f2fs-dev] [syzbot] [f2fs?] INFO: task hung in f2fs_fallocate (6)
Date: Wed, 25 Feb 2026 22:18:20 -0800 [thread overview]
Message-ID: <699fe5ac.050a0220.2fcbed.0003.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d4906ae14a5f Add linux-next specific files for 20260220
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f24006580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cdf9388b212a2b28
dashboard link: https://syzkaller.appspot.com/bug?extid=73d18077a2323a1fdb5e
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1312395a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a4855a580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1537e9684d19/disk-d4906ae1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd6c9977a9cf/vmlinux-d4906ae1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f1d85a2d6c78/bzImage-d4906ae1.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2471b6f6a299/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=149a0202580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+73d18077a2323a1fdb5e@syzkaller.appspotmail.com
INFO: task syz.1.18:6046 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.18 state:D stack:28832 pid:6046 tgid:6042 ppid:6019 task_flags:0x400040 flags:0x00080002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5295 [inline]
__schedule+0x1585/0x5340 kernel/sched/core.c:6907
__schedule_loop kernel/sched/core.c:6989 [inline]
schedule+0x164/0x360 kernel/sched/core.c:7004
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7061
rwsem_down_write_slowpath+0x899/0x1040 kernel/locking/rwsem.c:1185
__down_write_common kernel/locking/rwsem.c:1317 [inline]
__down_write kernel/locking/rwsem.c:1326 [inline]
down_write+0x1bc/0x200 kernel/locking/rwsem.c:1591
inode_lock include/linux/fs.h:1028 [inline]
f2fs_fallocate+0x24e/0x9b0 fs/f2fs/file.c:2013
vfs_fallocate+0x669/0x7e0 fs/open.c:340
ksys_fallocate fs/open.c:364 [inline]
__do_sys_fallocate fs/open.c:369 [inline]
__se_sys_fallocate fs/open.c:367 [inline]
__x64_sys_fallocate+0xc0/0x110 fs/open.c:367
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa61c59c629
RSP: 002b:00007fa61d448028 EFLAGS: 00000246
ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fa61c816090 RCX: 00007fa61c59c629
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 00007fa61c632b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa61c816128 R14: 00007fa61c816090 R15: 00007ffcfdb9b178
</TASK>
Showing all locks held in the system:
---
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 syzkaller@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 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.
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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+73d18077a2323a1fdb5e@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [f2fs?] INFO: task hung in f2fs_fallocate (6)
Date: Wed, 25 Feb 2026 22:18:20 -0800 [thread overview]
Message-ID: <699fe5ac.050a0220.2fcbed.0003.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d4906ae14a5f Add linux-next specific files for 20260220
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f24006580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cdf9388b212a2b28
dashboard link: https://syzkaller.appspot.com/bug?extid=73d18077a2323a1fdb5e
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1312395a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a4855a580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1537e9684d19/disk-d4906ae1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd6c9977a9cf/vmlinux-d4906ae1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f1d85a2d6c78/bzImage-d4906ae1.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2471b6f6a299/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=149a0202580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+73d18077a2323a1fdb5e@syzkaller.appspotmail.com
INFO: task syz.1.18:6046 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.18 state:D stack:28832 pid:6046 tgid:6042 ppid:6019 task_flags:0x400040 flags:0x00080002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5295 [inline]
__schedule+0x1585/0x5340 kernel/sched/core.c:6907
__schedule_loop kernel/sched/core.c:6989 [inline]
schedule+0x164/0x360 kernel/sched/core.c:7004
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7061
rwsem_down_write_slowpath+0x899/0x1040 kernel/locking/rwsem.c:1185
__down_write_common kernel/locking/rwsem.c:1317 [inline]
__down_write kernel/locking/rwsem.c:1326 [inline]
down_write+0x1bc/0x200 kernel/locking/rwsem.c:1591
inode_lock include/linux/fs.h:1028 [inline]
f2fs_fallocate+0x24e/0x9b0 fs/f2fs/file.c:2013
vfs_fallocate+0x669/0x7e0 fs/open.c:340
ksys_fallocate fs/open.c:364 [inline]
__do_sys_fallocate fs/open.c:369 [inline]
__se_sys_fallocate fs/open.c:367 [inline]
__x64_sys_fallocate+0xc0/0x110 fs/open.c:367
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa61c59c629
RSP: 002b:00007fa61d448028 EFLAGS: 00000246
ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fa61c816090 RCX: 00007fa61c59c629
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 00007fa61c632b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa61c816128 R14: 00007fa61c816090 R15: 00007ffcfdb9b178
</TASK>
Showing all locks held in the system:
---
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 syzkaller@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 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.
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
next reply other threads:[~2026-02-26 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 6:18 syzbot [this message]
2026-02-26 6:18 ` [syzbot] [f2fs?] INFO: task hung in f2fs_fallocate (6) syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=699fe5ac.050a0220.2fcbed.0003.GAE@google.com \
--to=syzbot+73d18077a2323a1fdb5e@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.