syzbot


INFO: task hung in flush_async_commits

Status: auto-obsoleted due to no activity on 2023/05/05 20:14
Subsystems: reiserfs
[Documentation on labels]
First crash: 651d, last: 601d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in flush_async_commits 2 53d 117d 0/3 upstream: reported on 2024/06/02 16:31
upstream INFO: task hung in flush_async_commits (2) reiserfs 3 364d 432d 0/28 auto-obsoleted due to no activity on 2023/12/28 15:52

Sample crash report:
INFO: task kworker/1:3:5165 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc6-syzkaller-00239-g0136d86b7852 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:3     state:D stack:24760 pid:5165  ppid:2      flags:0x00004000
Workqueue: reiserfs/loop1 flush_async_commits
Call Trace:
 <TASK>
 __schedule+0x13ca/0x43c0
 schedule+0xc3/0x190
 schedule_preempt_disabled+0x13/0x20
 __mutex_lock_common+0xdb6/0x2630
 mutex_lock_nested+0x1b/0x20
 reiserfs_write_lock+0x7a/0xd0
 flush_async_commits+0x46/0xc0
 process_one_work+0x96c/0x13e0
 worker_thread+0xa63/0x1210
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>

Showing all locks held in the system:
2 locks held by kworker/u4:0/9:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cf26e10 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xce0
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cf27610 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xce0
1 lock held by khungtaskd/28:
 #0: ffffffff8cf26c40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/4747:
 #0: ffff888027f62098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70
 #1: ffffc900015802f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x53b/0x1630
3 locks held by kworker/1:3/5165:
 #0: ffff88802d10f138 ((wq_completion)reiserfs/loop1){+.+.}-{0:0}, at: process_one_work+0x7eb/0x13e0
 #1: ffffc90004977d20 ((work_completion)(&(&journal->j_work)->work)){+.+.}-{0:0}, at: process_one_work+0x835/0x13e0
 #2: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
4 locks held by kworker/0:6/5170:
 #0: ffff888012471538 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x7eb/0x13e0
 #1: ffffc900049d7d20 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x835/0x13e0
 #2: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: flush_old_commits+0xcb/0x2e0
 #3: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
3 locks held by syz-executor.1/10008:
2 locks held by syz-executor.1/10771:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
2 locks held by syz-executor.2/10793:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
2 locks held by syz-executor.2/10836:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
2 locks held by syz-executor.2/10837:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
2 locks held by syz-executor.2/10937:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
2 locks held by syz-executor.2/10965:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0
2 locks held by syz-executor.1/10952:
 #0: ffff8880204120e0 (&type->s_umount_key#94){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0
 #1: ffff888022923090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.2.0-rc6-syzkaller-00239-g0136d86b7852 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Call Trace:
 <TASK>
 dump_stack_lvl+0x1b5/0x2a0
 nmi_cpu_backtrace+0x47b/0x500
 nmi_trigger_cpumask_backtrace+0x1d3/0x430
 watchdog+0xf70/0xfb0
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 33 Comm: kworker/u4:2 Not tainted 6.2.0-rc6-syzkaller-00239-g0136d86b7852 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Workqueue: phy11 ieee80211_iface_work
RIP: 0010:ieee802_11_parse_elems_full+0x5e/0x2490
Code: 00 00 00 fc ff df 48 c7 84 24 40 01 00 00 b3 8a b5 41 48 c7 84 24 48 01 00 00 3c bb a4 8c 48 c7 84 24 50 01 00 00 f0 3c 20 8a <4c> 8d a4 24 40 01 00 00 49 c1 ec 03 48 b8 f1 f1 f1 f1 01 f2 00 00
RSP: 0018:ffffc90000aa7660 EFLAGS: 00000286
RAX: 2ac0867fe4562e00 RBX: ffffc90000aa7b20 RCX: dffffc0000000000
RDX: ffff888012638000 RSI: 000000000000004c RDI: ffffc90000aa7b20
RBP: ffffc90000aa78f0 R08: ffffffff8a13d82f R09: ffffffff8a13d555
R10: 0000000000000006 R11: ffff888012638000 R12: ffff888031289ae0
R13: ffff888031288c80 R14: ffffc90000aa7b20 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055fd419d7150 CR3: 0000000029abe000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ieee80211_ibss_rx_queued_mgmt+0x5ba/0x2fb0
 ieee80211_iface_work+0x7bd/0xd00
 process_one_work+0x96c/0x13e0
 worker_thread+0xa63/0x1210
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/02/04 20:05 upstream 0136d86b7852 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in flush_async_commits
2023/01/28 13:32 upstream 5af6ce704936 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in flush_async_commits
2023/01/26 07:23 upstream 7c46948a6e9c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in flush_async_commits
2022/12/16 16:27 upstream 84e57d292203 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in flush_async_commits
* Struck through repros no longer work on HEAD.