syzbot


INFO: task can't die in corrupted

Status: fixed on 2020/11/16 12:12
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+ee250ac8137be41d7b13@syzkaller.appspotmail.com
Fix commit: 86f33603f8c5 f2fs: handle errors of f2fs_get_meta_page_nofail
First crash: 1357d, last: 1330d
Cause bisection: introduced by (bisect log) :
commit eede846af512572b1f30b34f9889d7df64c017d4
Author: Jaegeuk Kim <jaegeuk@kernel.org>
Date: Fri Oct 2 21:17:35 2020 +0000

  f2fs: f2fs_get_meta_page_nofail should not be failed

Crash: no output from test machine (log)
Repro: C syz .config
  
Duplicate bugs (1)
duplicates (1):
Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
INFO: task can't die in congestion_wait mm 3 1357d 1353d 0/27 closed as dup on 2020/10/10 16:27
Discussions (7)
Title Replies (including bot) Last reply
[PATCH AUTOSEL 5.9 001/147] powerpc/vmemmap: Fix memory leak with vmemmap list allocation failures. 154 (154) 2020/11/05 21:18
[PATCH 5.9 000/391] 5.9.4-rc1 review 406 (406) 2020/11/05 16:26
[PATCH 5.4 000/214] 5.4.75-rc1 review 219 (219) 2020/11/04 17:50
[PATCH AUTOSEL 5.4 01/80] powerpc/powernv/smp: Fix spurious DBG() warning 81 (81) 2020/10/27 12:01
[PATCH AUTOSEL 5.8 001/132] powerpc/powernv/smp: Fix spurious DBG() warning 133 (133) 2020/10/27 11:40
[PATCH] f2fs: f2fs_get_meta_page_nofail should not be failed 4 (4) 2020/10/14 06:21
INFO: task can't die in corrupted 10 (11) 2020/10/13 03:08
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task can't die in corrupted (2) kernel C error error 57 1d15h 1291d 0/27 upstream: reported C repro on 2020/12/11 10:03

Sample crash report:
INFO: task syz-executor705:8522 can't die for more than 143 seconds.
task:syz-executor705 state:R  running task     stack:27448 pid: 8522 ppid:  8521 flags:0x00004006
Call Trace:

Showing all locks held in the system:
1 lock held by khungtaskd/1657:
 #0: ffffffff8b338160 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6253
1 lock held by in:imklog/8201:
 #0: ffff88801b65a370 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0xe9/0x100 fs/file.c:932
1 lock held by syz-executor705/8522:

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

Kernel panic - not syncing: hung_task: blocked tasks
CPU: 0 PID: 1657 Comm: khungtaskd Not tainted 5.10.0-rc1-next-20201102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x107/0x163 lib/dump_stack.c:118
 panic+0x306/0x73d kernel/panic.c:231
 check_hung_uninterruptible_tasks kernel/hung_task.c:257 [inline]
 watchdog.cold+0x23e/0x248 kernel/hung_task.c:338
 kthread+0x3af/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/11/02 23:50 linux-next b49976d8ef64 8bc4594f .config console log report syz C ci-upstream-linux-next-kasan-gce-root
2020/10/08 02:32 linux-next 8b787da7ba8c 1880b4a9 .config console log report syz C ci-upstream-linux-next-kasan-gce-root
2020/10/07 05:12 linux-next a804ab086e9d 1880b4a9 .config console log report syz C ci-upstream-linux-next-kasan-gce-root
2020/10/06 20:59 linux-next a804ab086e9d 1880b4a9 .config console log report syz C ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.