syzbot


INFO: task hung in __bread_gfp (2)

Status: upstream: reported C repro on 2025/01/05 12:56
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+77d1a6abf8e02c30571a@syzkaller.appspotmail.com
First crash: 9d19h, last: 8d03h
Bug presence (2)
Date Name Commit Repro Result
2025/01/07 linux-5.15.y (ToT) 91786f140358 C [report] INFO: task hung in __bread_gfp
2025/01/07 upstream (ToT) fbfd64d25c7a C Didn't crash
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in __bread_gfp (5) ntfs3 1 259d 259d 0/28 auto-obsoleted due to no activity on 2024/07/30 08:01
upstream INFO: task hung in __bread_gfp (3) fs 1 1166d 1166d 0/28 auto-closed as invalid on 2022/02/04 04:37
upstream INFO: task hung in __bread_gfp exfat 4 2383d 2478d 0/28 auto-closed as invalid on 2019/02/22 10:29
linux-5.15 INFO: task hung in __bread_gfp 3 271d 285d 0/3 auto-obsoleted due to no activity on 2024/07/28 07:35
android-49 INFO: task hung in __bread_gfp 2 2464d 2478d 0/3 auto-closed as invalid on 2019/02/22 14:34
upstream INFO: task hung in __bread_gfp (2) jfs 5 1700d 1706d 0/28 auto-closed as invalid on 2020/07/20 01:01
upstream INFO: task hung in __bread_gfp (4) reiserfs C error 3 691d 752d 0/28 auto-obsoleted due to no activity on 2023/07/25 23:59

Sample crash report:
INFO: task syz-executor596:4162 blocked for more than 143 seconds.
      Not tainted 5.15.175-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor596 state:D stack:26136 pid: 4162 ppid:  4161 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5027 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6373
 schedule+0x11b/0x1f0 kernel/sched/core.c:6456
 io_schedule+0x88/0x100 kernel/sched/core.c:8481
 bit_wait_io+0xe/0xc0 kernel/sched/wait_bit.c:209
 __wait_on_bit+0xb9/0x180 kernel/sched/wait_bit.c:49
 out_of_line_wait_on_bit+0x1d0/0x250 kernel/sched/wait_bit.c:64
 wait_on_bit_io include/linux/wait_bit.h:101 [inline]
 __wait_on_buffer fs/buffer.c:122 [inline]
 wait_on_buffer include/linux/buffer_head.h:390 [inline]
 __bread_slow fs/buffer.c:1181 [inline]
 __bread_gfp+0x2d6/0x390 fs/buffer.c:1384
 sb_bread include/linux/buffer_head.h:337 [inline]
 qnx6_check_first_superblock+0xa2/0x320 fs/qnx6/inode.c:265
 qnx6_fill_super+0x349/0x19c0 fs/qnx6/inode.c:335
 mount_bdev+0x2c9/0x3f0 fs/super.c:1400
 legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x2ba/0xb40 fs/namespace.c:3012
 do_mount fs/namespace.c:3355 [inline]
 __do_sys_mount fs/namespace.c:3563 [inline]
 __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3540
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f42169ab939
RSP: 002b:00007fff43350218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f42169f4078 RCX: 00007f42169ab939
RDX: 0000000020000580 RSI: 0000000020000480 RDI: 0000000020000440
RBP: 00007f4216a1e5f0 R08: 0000000000000000 R09: 0000000000000006
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000001
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8cb1fd20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3930:
 #0: ffff88814ce57098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cd62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor596/4162:
 #0: ffff8880769800e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:295
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:108 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:562

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/06 03:47 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __bread_gfp
2025/01/05 22:55 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __bread_gfp
2025/01/05 17:49 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __bread_gfp
2025/01/05 12:55 linux-5.15.y 91786f140358 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in __bread_gfp
* Struck through repros no longer work on HEAD.