INFO: task hung in ext4_fill_super

5 views
Skip to first unread message

syzbot

unread,
Aug 9, 2021, 11:53:19 AM8/9/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 46914f96189b Linux 4.14.243
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11812e26300000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d036f77f7dc4ac4
dashboard link: https://syzkaller.appspot.com/bug?extid=651008a32cea658f8d7e
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=147eb1e9300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14cb8eaa300000

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

EXT4-fs (loop3): feature flags set on rev 0 fs, running e2fsck is recommended
EXT4-fs error (device loop3): ext4_get_journal_inode:4623: comm syz-executor032: inode #836960256: comm syz-executor032: iget: illegal inode #
EXT4-fs (loop3): no journal found
INFO: task syz-executor032:9065 blocked for more than 140 seconds.
Not tainted 4.14.243-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor032 D27912 9065 7958 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 kernel/time/timer.c:1724
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 kernel/sched/completion.c:123
kthread_stop+0xce/0x640 kernel/kthread.c:555
ext4_fill_super+0x6880/0xb290 fs/ext4/super.c:4561
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x445c0a
RSP: 002b:00007fffe35773b8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fffe3577410 RCX: 0000000000445c0a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fffe35773d0
RBP: 00007fffe35773d0 R08: 00007fffe3577410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200003f8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000005
INFO: task syz-executor032:9080 blocked for more than 140 seconds.
Not tainted 4.14.243-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor032 D27912 9080 7959 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 kernel/time/timer.c:1724
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 kernel/sched/completion.c:123
kthread_stop+0xce/0x640 kernel/kthread.c:555
ext4_fill_super+0x6880/0xb290 fs/ext4/super.c:4561
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x445c0a
RSP: 002b:00007fffe35773b8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fffe3577410 RCX: 0000000000445c0a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fffe35773d0
RBP: 00007fffe35773d0 R08: 00007fffe3577410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200003f8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000005
INFO: task syz-executor032:9509 blocked for more than 140 seconds.
Not tainted 4.14.243-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor032 D27912 9509 7956 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 kernel/time/timer.c:1724
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 kernel/sched/completion.c:123
kthread_stop+0xce/0x640 kernel/kthread.c:555
ext4_fill_super+0x6880/0xb290 fs/ext4/super.c:4561
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x445c0a
RSP: 002b:00007fffe35773b8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fffe3577410 RCX: 0000000000445c0a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fffe35773d0
RBP: 00007fffe35773d0 R08: 00007fffe3577410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200003f8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000005
INFO: task syz-executor032:9670 blocked for more than 140 seconds.
Not tainted 4.14.243-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor032 D27912 9670 7954 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 kernel/time/timer.c:1724
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 kernel/sched/completion.c:123
kthread_stop+0xce/0x640 kernel/kthread.c:555
ext4_fill_super+0x6880/0xb290 fs/ext4/super.c:4561
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x445c0a
RSP: 002b:00007fffe35773b8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fffe3577410 RCX: 0000000000445c0a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fffe35773d0
RBP: 00007fffe35773d0 R08: 00007fffe3577410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200003f8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000005
INFO: task syz-executor032:11534 blocked for more than 140 seconds.
Not tainted 4.14.243-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor032 D27912 11534 7955 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 kernel/time/timer.c:1724
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 kernel/sched/completion.c:123
kthread_stop+0xce/0x640 kernel/kthread.c:555
ext4_fill_super+0x6880/0xb290 fs/ext4/super.c:4561
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x445c0a
RSP: 002b:00007fffe35773b8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fffe3577410 RCX: 0000000000445c0a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fffe35773d0
RBP: 00007fffe35773d0 R08: 00007fffe3577410 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200003f8
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000005

Showing all locks held in the system:
1 lock held by khungtaskd/1526:
#0: (tasklist_lock){.+.+}, at: [<ffffffff87012a3c>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
1 lock held by in:imklog/7740:
#0: (&f->f_pos_lock){+.+.}, at: [<ffffffff818d3ecb>] __fdget_pos+0x1fb/0x2b0 fs/file.c:769
1 lock held by syz-executor032/9065:
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] sget_userns+0x556/0xc10 fs/super.c:516
1 lock held by syz-executor032/9080:
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] sget_userns+0x556/0xc10 fs/super.c:516
1 lock held by syz-executor032/9509:
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] sget_userns+0x556/0xc10 fs/super.c:516
1 lock held by syz-executor032/9670:
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] sget_userns+0x556/0xc10 fs/super.c:516
1 lock held by syz-executor032/11534:
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] sget_userns+0x556/0xc10 fs/super.c:516
1 lock held by syz-executor032/23381:
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#25/1){+.+.}, at: [<ffffffff81874346>] sget_userns+0x556/0xc10 fs/super.c:516

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

NMI backtrace for cpu 1
CPU: 1 PID: 1526 Comm: khungtaskd Not tainted 4.14.243-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x180 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:195 [inline]
watchdog+0x5b9/0xb40 kernel/hung_task.c:274
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4620 Comm: systemd-journal Not tainted 4.14.243-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880a1590040 task.stack: ffff8880a1598000
RIP: 0033:0x7f663edacc22
RSP: 002b:00007ffe3f5230a0 EFLAGS: 00000206
RAX: 0000000000000006 RBX: 0000000000130388 RCX: 0000000000130388
RDX: 0000000000000003 RSI: 0000000000000010 RDI: 000056228bc54120
RBP: 000056228bc50040 R08: 00000000000000e8 R09: 000056228bc54120
R10: 001984fbdb25f2ae R11: 00007f663c7cfd70 R12: 0000000000000006
R13: 0000000000000003 R14: 0000000000000010 R15: 000056228bc54420
FS: 00007f663f1778c0(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f663c7cf000 CR3: 00000000a217e000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages