syzbot


INFO: task hung in sync_inodes_sb (2)

Status: upstream: reported C repro on 2021/01/07 19:48
Subsystems: vfs
[Documentation on labels]
Reported-by: syzbot+d72364f87ba3a6d6eec1@syzkaller.appspotmail.com
First crash: 1176d, last: 408d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in sync_inodes_sb origin:upstream missing-backport C error 63 47d 385d 0/3 upstream: reported C repro on 2023/03/10 02:13
upstream INFO: task hung in sync_inodes_sb (5) ext4 C error inconclusive 150 39d 255d 0/26 upstream: reported C repro on 2023/07/18 04:00
upstream INFO: task hung in sync_inodes_sb (2) fs 4 1803d 1820d 0/26 auto-closed as invalid on 2019/10/19 16:22
upstream INFO: task hung in sync_inodes_sb (3) fs mm C done 6 1546d 1554d 15/26 fixed on 2020/02/14 01:19
upstream INFO: task hung in sync_inodes_sb fs 58 1900d 2138d 0/26 closed as dup on 2018/09/08 15:37
linux-4.14 INFO: task hung in sync_inodes_sb 1 1515d 1515d 0/1 auto-closed as invalid on 2020/06/02 17:26
android-49 INFO: task hung in sync_inodes_sb 11 2040d 2119d 0/3 auto-closed as invalid on 2019/02/24 06:19
android-49 INFO: task hung in sync_inodes_sb (2) 2 1629d 1791d 0/3 auto-closed as invalid on 2020/02/10 00:14
upstream INFO: task hung in sync_inodes_sb (4) nilfs C done inconclusive 345 269d 1224d 23/26 fixed on 2023/07/04 09:17
linux-6.1 INFO: task hung in sync_inodes_sb origin:upstream missing-backport C 51 11d 385d 0/3 upstream: reported C repro on 2023/03/10 02:07
linux-4.19 INFO: task hung in sync_inodes_sb xfs C error 13 427d 1267d 0/1 upstream: reported C repro on 2020/10/09 07:19
Fix bisection attempts (22)
Created Duration User Patch Repo Result
2023/01/29 21:21 25m bisect fix linux-4.14.y job log (0) log
2022/09/15 22:15 29m bisect fix linux-4.14.y job log (0) log
2022/08/16 21:46 28m bisect fix linux-4.14.y job log (0) log
2022/07/17 21:20 26m bisect fix linux-4.14.y job log (0) log
2022/06/17 20:51 28m bisect fix linux-4.14.y job log (0) log
2022/05/18 19:02 30m bisect fix linux-4.14.y job log (0) log
2022/04/18 18:07 30m bisect fix linux-4.14.y job log (0) log
2022/03/19 17:26 29m bisect fix linux-4.14.y job log (0) log
2022/02/17 16:57 27m bisect fix linux-4.14.y job log (0) log
2022/01/18 16:27 29m bisect fix linux-4.14.y job log (0) log
2021/12/19 15:56 31m bisect fix linux-4.14.y job log (0) log
2021/11/19 15:26 30m bisect fix linux-4.14.y job log (0) log
2021/10/20 13:54 24m bisect fix linux-4.14.y job log (0) log
2021/09/20 13:28 26m bisect fix linux-4.14.y job log (0) log
2021/08/21 13:02 26m bisect fix linux-4.14.y job log (0) log
2021/07/22 12:31 30m bisect fix linux-4.14.y job log (0) log
2021/06/22 09:59 32m bisect fix linux-4.14.y job log (0) log
2021/05/22 17:45 31m bisect fix linux-4.14.y job log (0) log
2021/03/24 04:35 28m bisect fix linux-4.14.y job log (0) log
2021/02/22 04:03 28m bisect fix linux-4.14.y job log (0) log
2021/02/18 13:32 18m bisect fix linux-4.14.y error job log (0)
2021/02/11 13:41 0m bisect fix linux-4.14.y error job log (0)

Sample crash report:
F2FS-fs (loop0): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 12
F2FS-fs (loop0): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 12
F2FS-fs (loop0): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 12
INFO: task syz-executor385:7969 blocked for more than 140 seconds.
      Not tainted 4.14.296-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor385 D28912  7969   7957 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2811 [inline]
 __schedule+0x88b/0x1de0 kernel/sched/core.c:3387
 schedule+0x8d/0x1b0 kernel/sched/core.c:3431
 wb_wait_for_completion fs/fs-writeback.c:222 [inline]
 wb_wait_for_completion+0x118/0x170 fs/fs-writeback.c:218
 sync_inodes_sb+0x173/0x880 fs/fs-writeback.c:2447
 sync_inodes_one_sb+0x3d/0x50 fs/sync.c:74
 iterate_supers+0x124/0x490 fs/super.c:613
 sys_sync+0x78/0x130 fs/sync.c:113
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f8c80fa6569
RSP: 002b:00007fff4e5709b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 0000000020010ba0 RCX: 00007f8c80fa6569
RDX: 00007f8c80f64463 RSI: 0000000000000003 RDI: 0000000000004c00
RBP: 0000000000000000 R08: 0000555556e7a2c0 R09: 00007f8c81015ec0
R10: 00007fff4e5706c0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff4e5709cc R14: 431bde82d7b634db R15: 0000000000000000

Showing all locks held in the system:
1 lock held by khungtaskd/1527:
 #0:  (tasklist_lock){.+.+}, at: [<ffffffff87028579>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
2 locks held by syz-executor385/7969:
 #0:  (&type->s_umount_key#61){.+.+}, at: [<ffffffff8187a25a>] iterate_supers+0xda/0x490 fs/super.c:611
 #1:  (&bdi->wb_switch_rwsem){+.+.}, at: [<ffffffff8190de16>] bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
 #1:  (&bdi->wb_switch_rwsem){+.+.}, at: [<ffffffff8190de16>] sync_inodes_sb+0x156/0x880 fs/fs-writeback.c:2445

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

NMI backtrace for cpu 0
CPU: 0 PID: 1527 Comm: khungtaskd Not tainted 4.14.296-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4613 Comm: systemd-journal Not tainted 4.14.296-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
task: ffff8880a1fac580 task.stack: ffff8880a1fb0000
RIP: 0010:debug_spin_unlock kernel/locking/spinlock_debug.c:100 [inline]
RIP: 0010:do_raw_spin_unlock+0xc3/0x220 kernel/locking/spinlock_debug.c:134
RSP: 0018:ffff8880a1fb7d78 EFLAGS: 00000a06
RAX: 0000000000000000 RBX: ffff8880a1e14000 RCX: 1ffff110143f59c1
RDX: 1ffff110143c2821 RSI: 0000000000000001 RDI: ffff8880a1e14104
RBP: ffff8880a1e14100 R08: ffffffff8b9a92a8 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880a1fac580 R12: ffff8880a1e14108
R13: ffff8880a1e14110 R14: ffff8880a1e14100 R15: 0000000000000000
FS:  00007fdf23cfb8c0(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdf210f5000 CR3: 00000000a1d7f000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 __raw_spin_unlock include/linux/spinlock_api_smp.h:151 [inline]
 _raw_spin_unlock+0x1f/0x40 kernel/locking/spinlock.c:184
 spin_unlock include/linux/spinlock.h:357 [inline]
 timerfd_setup_cancel fs/timerfd.c:157 [inline]
 do_timerfd_settime.part.0+0x1a1/0xde0 fs/timerfd.c:457
 do_timerfd_settime fs/timerfd.c:535 [inline]
 SYSC_timerfd_settime fs/timerfd.c:544 [inline]
 SyS_timerfd_settime+0xe8/0x170 fs/timerfd.c:535
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fdf22fc47ba
RSP: 002b:00007ffc0b49b3e8 EFLAGS: 00000246 ORIG_RAX: 000000000000011e
RAX: ffffffffffffffda RBX: 00005617d5dc0250 RCX: 00007fdf22fc47ba
RDX: 00007ffc0b49b400 RSI: 0000000000000001 RDI: 000000000000000f
RBP: 000000003ec3ee00 R08: 431bde82d7b634db R09: 00000101eef6e890
R10: 0000000000000000 R11: 0000000000000246 R12: 000000003ec2cbf1
R13: 00007fdf239fd147 R14: 00007fdf23a5a800 R15: 0005ec44ef4137ba
Code: 48 8b 04 25 c0 7f 02 00 48 39 45 10 0f 85 d6 00 00 00 4c 8d 65 08 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 0f b6 04 02 <84> c0 74 08 3c 03 0f 8e fc 00 00 00 65 8b 05 1a ca bf 7e 39 45 

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/30 18:49 linux-4.14.y 41f36d7859a7 2a71366b .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2022/10/22 20:01 linux-4.14.y 9d5c0b3a8e1a c0b80a55 .config console log report syz C [disk image] [vmlinux] [mounted in repro] ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2021/01/08 05:17 linux-4.14.y 1752938529c6 c104d4a3 .config console log report syz C ci2-linux-4-14
2023/02/14 13:47 linux-4.14.y a8ad60f2af58 93ae7e0a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2022/12/02 10:18 linux-4.14.y 179ef7fe8677 e080de16 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2022/12/01 07:53 linux-4.14.y 179ef7fe8677 4c2a66e8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2021/04/22 17:08 linux-4.14.y cf256fbcbe34 33c28d03 .config console log report info ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2021/04/09 12:45 linux-4.14.y 0cc244011f40 6a81331a .config console log report info ci2-linux-4-14 INFO: task hung in sync_inodes_sb
2021/01/12 13:13 linux-4.14.y ec822b3e8bf4 2c1f2513 .config console log report info ci2-linux-4-14
2021/01/08 02:53 linux-4.14.y 1752938529c6 c104d4a3 .config console log report info ci2-linux-4-14
2021/01/07 19:47 linux-4.14.y 1752938529c6 c104d4a3 .config console log report info ci2-linux-4-14
* Struck through repros no longer work on HEAD.