syzbot


INFO: task hung in blkdev_fallocate

Status: upstream: reported C repro on 2023/03/12 23:16
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+d1600ddb4950c2beebf5@syzkaller.appspotmail.com
First crash: 607d, last: 2d06h
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2023/05/06 upstream (ToT) 2e1e1337881b C [report] INFO: task hung in blkdev_fallocate
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in blkdev_fallocate origin:upstream C error 24 44d 611d 0/3 upstream: reported C repro on 2023/03/08 05:38
upstream INFO: task hung in blkdev_fallocate block C error error 1641 3d00h 1040d 0/28 upstream: reported C repro on 2022/01/03 09:11
Last patch testing requests (9)
Created Duration User Patch Repo Result
2024/11/06 15:26 1h14m retest repro linux-5.15.y report log
2024/10/23 10:33 17m retest repro linux-5.15.y report log
2024/10/23 10:33 1h06m retest repro linux-5.15.y report log
2024/10/23 10:33 1h00m retest repro linux-5.15.y report log
2024/10/09 04:37 13m retest repro linux-5.15.y report log
2024/10/09 04:37 11m retest repro linux-5.15.y report log
2024/10/09 04:37 15m retest repro linux-5.15.y report log
2024/10/09 04:37 12m retest repro linux-5.15.y report log
2024/10/09 04:37 1h05m retest repro linux-5.15.y report log
Fix bisection attempts (3)
Created Duration User Patch Repo Result
2023/10/11 04:56 0m bisect fix linux-5.15.y error job log
2023/06/28 01:43 1h06m bisect fix linux-5.15.y OK (0) job log log
2023/04/26 04:45 47m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
INFO: task syz-executor145:3589 blocked for more than 143 seconds.
      Not tainted 5.15.167-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor145 state:D stack:27168 pid: 3589 ppid:  3585 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
 rwsem_down_write_slowpath+0xf0c/0x16a0 kernel/locking/rwsem.c:1165
 filemap_invalidate_lock include/linux/fs.h:834 [inline]
 blkdev_fallocate+0x25e/0x4e0 block/fops.c:600
 vfs_fallocate+0x54a/0x6b0 fs/open.c:308
 ksys_fallocate fs/open.c:331 [inline]
 __do_sys_fallocate fs/open.c:339 [inline]
 __se_sys_fallocate fs/open.c:337 [inline]
 __x64_sys_fallocate+0xb9/0x100 fs/open.c:337
 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:0x7fc77b299b29
RSP: 002b:00007ffc58285178 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc77b299b29
RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000000000000004
RBP: 00000000000f4240 R08: 00000000000000a0 R09: 00000000000000a0
R10: 0000002000000400 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffc58285398 R14: 00007ffc582851a0 R15: 00007ffc58285190
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c91fc60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by klogd/3015:
2 locks held by getty/3332:
 #0: ffff888029f81098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc9000229b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor145/3588:
1 lock held by syz-executor145/3589:
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x25e/0x4e0 block/fops.c:600
1 lock held by syz-executor145/3590:
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x25e/0x4e0 block/fops.c:600
1 lock held by syz-executor145/3597:
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x25e/0x4e0 block/fops.c:600
1 lock held by syz-executor145/3598:
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
 #0: ffff88814088acb8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x25e/0x4e0 block/fops.c:600

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/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
CPU: 1 PID: 3008 Comm: syslogd Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:__lock_is_held kernel/locking/lockdep.c:5367 [inline]
RIP: 0010:lock_is_held_type+0xd2/0x180 kernel/locking/lockdep.c:5666
Code: 48 ff c3 49 63 85 e8 0a 00 00 48 83 c5 28 48 39 c3 7c d8 eb 11 48 c7 c7 20 f3 7e 8c 48 89 de e8 f4 d8 f6 f9 eb cb 31 ed eb 1f <41> 83 fe ff 74 14 31 c0 f6 45 22 03 0f 95 c0 31 ed 44 39 f0 40 0f
RSP: 0018:ffffc900024f72b0 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000000 RCX: dffffc0000000000
RDX: 0000000000000009 RSI: ffff8880b913a318 RDI: ffff88807dc74670
RBP: ffff88807dc74670 R08: dffffc0000000000 R09: fffffbfff1bd2c16
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000046
R13: ffff88807dc73b80 R14: 00000000ffffffff R15: ffff8880b913a318
FS:  00007f38c637a380(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b3828b8600 CR3: 000000002384a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 lock_is_held include/linux/lockdep.h:287 [inline]
 lockdep_assert_rq_held kernel/sched/sched.h:1317 [inline]
 rq_clock_task kernel/sched/sched.h:1477 [inline]
 update_curr+0x10c/0xa50 kernel/sched/fair.c:828
 dequeue_entity+0x27/0xfe0 kernel/sched/fair.c:4568
 dequeue_task_fair+0x270/0x13c0 kernel/sched/fair.c:5922
 dequeue_task kernel/sched/core.c:1994 [inline]
 deactivate_task kernel/sched/core.c:2011 [inline]
 __schedule+0x786/0x45b0 kernel/sched/core.c:6327
 schedule+0x11b/0x1f0 kernel/sched/core.c:6456
 schedule_timeout+0xac/0x300 kernel/time/timer.c:1890
 __skb_wait_for_more_packets+0x394/0x5f0 net/core/datagram.c:122
 __unix_dgram_recvmsg+0x351/0x1260 net/unix/af_unix.c:2317
 sock_recvmsg_nosec net/socket.c:966 [inline]
 sock_recvmsg net/socket.c:984 [inline]
 sock_read_iter+0x353/0x480 net/socket.c:1057
 call_read_iter include/linux/fs.h:2166 [inline]
 new_sync_read fs/read_write.c:404 [inline]
 vfs_read+0xa93/0xe10 fs/read_write.c:485
 ksys_read+0x1a2/0x2c0 fs/read_write.c:623
 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:0x7f38c64ceb6a
Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffd2727b7e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f38c64ceb6a
RDX: 00000000000000ff RSI: 000055a21f54f950 RDI: 0000000000000000
RBP: 000055a21f54f910 R08: 0000000000000001 R09: 0000000000000000
R10: 00007f38c666d3a3 R11: 0000000000000246 R12: 000055a21f54f99d
R13: 000055a21f54f950 R14: 0000000000000000 R15: 00007f38c66aba80
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.337 msecs

Crashes (30):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/09/24 09:48 linux-5.15.y 3a5928702e71 89298aad .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/04/06 17:44 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2023/05/27 23:44 linux-5.15.y 1fe619a7d252 cf184559 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2023/03/27 02:40 linux-5.15.y 115472395b0a fbf0499a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/05/17 06:01 linux-5.15.y 284087d4f7d5 c2e07261 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2024/04/26 04:46 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2024/04/07 01:37 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2023/05/07 22:47 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2023/03/13 02:39 linux-5.15.y bbf9f29bac04 5205ef30 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2024/09/24 08:36 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:35 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:33 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:29 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:28 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:26 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:22 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:20 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:19 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:15 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:14 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:07 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:05 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/09/24 08:04 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/01/25 12:21 linux-5.15.y ddcaf4999061 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2024/03/15 18:09 linux-5.15.y 574362648507 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2024/03/08 19:59 linux-5.15.y 574362648507 8e75c913 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2023/08/22 01:20 linux-5.15.y f6f7927ac664 6b415825 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in blkdev_fallocate
2023/03/14 10:29 linux-5.15.y 2ddbd0f967b3 0d5c4377 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2023/03/13 10:43 linux-5.15.y 2ddbd0f967b3 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
2023/03/12 23:15 linux-5.15.y bbf9f29bac04 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in blkdev_fallocate
* Struck through repros no longer work on HEAD.