syzbot

 sign-in | mailing list | source | docs
🐞 Open [979] ≡ Subsystems 🐞 Fixed [5236] 🐞 Invalid [12499] ⬇ Missing Backports [83] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

INFO: task hung in fuse_lookup

Status: closed as invalid on 2018/09/05 12:51
Subsystems: fuse
[Documentation on labels]
First crash: 2111d, last: 2059d
▶ ▼ Similar bugs (10)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 INFO: task hung in fuse_lookup 4 1667d 1819d 0/1 auto-closed as invalid on 2020/01/29 21:30
linux-4.19 INFO: task hung in fuse_lookup reiserfs C error 12 438d 1715d 0/1 upstream: reported C repro on 2019/08/14 05:24
linux-4.14 INFO: task hung in fuse_lookup (3) 1 830d 830d 0/1 auto-closed as invalid on 2022/05/15 00:47
linux-6.1 INFO: task hung in fuse_lookup origin:upstream syz 3 23d 322d 0/3 upstream: reported syz repro on 2023/06/07 05:32
upstream INFO: task hung in fuse_lookup (3) fuse C done error 46 7d12h 1715d 0/26 upstream: reported C repro on 2019/08/14 09:48
linux-5.15 INFO: task hung in fuse_lookup origin:upstream syz error 2 302d 322d 0/3 upstream: reported syz repro on 2023/06/07 02:49
linux-4.14 INFO: task hung in fuse_lookup (4) reiserfs C 2 443d 498d 0/1 upstream: reported C repro on 2022/12/13 09:09
linux-4.14 INFO: task hung in fuse_lookup (2) 1 1500d 1500d 0/1 auto-closed as invalid on 2020/07/13 23:30
android-49 INFO: task hung in fuse_lookup C 112 1629d 1840d 0/3 public: reported C repro on 2019/04/11 08:44
upstream INFO: task hung in fuse_lookup (2) fuse C 13 1893d 2053d 0/26 closed as dup on 2018/09/10 08:43

Sample crash report:
REISERFS warning (device loop6): sh-2011 read_super_block: can't find a reiserfs filesystem on (dev loop6, block 16, size 4096)
REISERFS warning (device loop6): sh-2021 reiserfs_fill_super: can not find reiserfs on loop6
REISERFS warning (device loop6): sh-2011 read_super_block: can't find a reiserfs filesystem on (dev loop6, block 16, size 4096)
REISERFS warning (device loop6): sh-2021 reiserfs_fill_super: can not find reiserfs on loop6
INFO: task syz-executor5:4685 blocked for more than 140 seconds.
      Not tainted 4.19.0-rc2+ #220
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D21248  4685      1 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2825 [inline]
 __schedule+0x87c/0x1df0 kernel/sched/core.c:3473
 schedule+0xfb/0x450 kernel/sched/core.c:3517
 schedule_preempt_disabled+0x10/0x20 kernel/sched/core.c:3575
 __mutex_lock_common kernel/locking/mutex.c:1003 [inline]
 __mutex_lock+0xbf9/0x1700 kernel/locking/mutex.c:1073
 mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1088
 fuse_lock_inode+0xba/0xf0 fs/fuse/inode.c:365
 fuse_lookup+0x8f/0x4c0 fs/fuse/dir.c:360
 __lookup_slow+0x2b5/0x540 fs/namei.c:1671
 lookup_slow+0x57/0x80 fs/namei.c:1688
 walk_component+0x94a/0x2630 fs/namei.c:1810
 link_path_walk.part.40+0xa6e/0x1540 fs/namei.c:2141
 link_path_walk fs/namei.c:2072 [inline]
 path_openat+0x268/0x5340 fs/namei.c:3533
 do_filp_open+0x255/0x380 fs/namei.c:3564
 do_sys_open+0x584/0x720 fs/open.c:1063
 __do_sys_open fs/open.c:1081 [inline]
 __se_sys_open fs/open.c:1076 [inline]
 __x64_sys_open+0x7e/0xc0 fs/open.c:1076
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4551a0
Code: 44 24 10 48 8b 4c 24 08 48 8b 54 24 70 48 39 d0 0f 85 69 01 00 00 48 8b 9c 24 10 01 00 00 48 89 1c 24 48 89 54 24 08 48 89 4c <24> 10 48 89 44 24 18 e8 74 6d 00 00 0f b6 44 24 20 84 c0 0f 84 3c
RSP: 002b:00007ffdddad73c0 EFLAGS: 00000206 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00000000004551a0
RDX: 0000000000000000 RSI: 0000000000090800 RDI: 00000000004c1e40
RBP: 000000000000182f R08: 0000000000000001 R09: 0000000001db4940
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000012
R13: 00000000001176de R14: 00000000000006f1 R15: badc0ffeebadface
INFO: task syz-executor5:6125 blocked for more than 140 seconds.
      Not tainted 4.19.0-rc2+ #220
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D22920  6125   4685 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2825 [inline]
 __schedule+0x87c/0x1df0 kernel/sched/core.c:3473
 schedule+0xfb/0x450 kernel/sched/core.c:3517
 request_wait_answer+0x4c8/0x920 fs/fuse/dev.c:474
 __fuse_request_send+0x12a/0x1d0 fs/fuse/dev.c:494
 fuse_request_send+0x62/0xa0 fs/fuse/dev.c:507
 fuse_simple_request+0x33d/0x730 fs/fuse/dev.c:565
 fuse_lookup_name+0x3ee/0x830 fs/fuse/dir.c:323
 fuse_lookup+0xff/0x4c0 fs/fuse/dir.c:361
 __lookup_slow+0x2b5/0x540 fs/namei.c:1671
 lookup_slow+0x57/0x80 fs/namei.c:1688
 walk_component+0x94a/0x2630 fs/namei.c:1810
 link_path_walk.part.40+0xa6e/0x1540 fs/namei.c:2141
 link_path_walk fs/namei.c:2072 [inline]
 path_openat+0x268/0x5340 fs/namei.c:3533
 do_filp_open+0x255/0x380 fs/namei.c:3564
 do_sys_open+0x584/0x720 fs/open.c:1063
 __do_sys_openat fs/open.c:1090 [inline]
 __se_sys_openat fs/open.c:1084 [inline]
 __x64_sys_openat+0x9d/0x100 fs/open.c:1084
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457099
Code: 48 8b 54 24 38 48 8b 7c 24 48 eb 8d 48 8b 6c 24 50 48 83 c4 58 c3 48 89 04 24 48 89 5c 24 08 e8 0d a9 fb ff 48 8b 44 24 40 48 <8b> 4c 24 48 48 8b 54 24 38 4c 8b 54 24 18 e9 ee fe ff ff 48 89 74
RSP: 002b:00007f2ea2131c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f2ea21326d4 RCX: 0000000000457099
RDX: 0000000000000002 RSI: 0000000020000100 RDI: ffffffffffffff9c
RBP: 0000000000930280 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d33f0 R14: 00000000004c8222 R15: 0000000000000003

Showing all locks held in the system:
1 lock held by khungtaskd/792:
 #0: 000000003507e4b4 (rcu_read_lock){....}, at: debug_show_all_locks+0xd0/0x428 kernel/locking/lockdep.c:4436
1 lock held by rs:main Q:Reg/4544:
 #0: 000000009b161038 (&rq->lock){-.-.}, at: idle_balance kernel/sched/fair.c:9452 [inline]
 #0: 000000009b161038 (&rq->lock){-.-.}, at: pick_next_task_fair+0xfb1/0x16e0 kernel/sched/fair.c:6620
1 lock held by rsyslogd/4546:
 #0: 00000000697e79b9 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x1bb/0x200 fs/file.c:766
2 locks held by getty/4637:
 #0: 00000000cc9b454c (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 000000001457ff64 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4638:
 #0: 00000000e75d6caa (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000bf828fe2 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4639:
 #0: 00000000802928d0 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 000000002d32e873 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4640:
 #0: 00000000eb4cd177 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000849152b2 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4641:
 #0: 000000001542cc81 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 000000005d1dd7e2 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4642:
 #0: 000000001c169451 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000cb084c5a (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by syz-executor5/4685:
 #0: 000000005248a2ce (&type->i_mutex_dir_key#6){++++}, at: inode_lock_shared include/linux/fs.h:748 [inline]
 #0: 000000005248a2ce (&type->i_mutex_dir_key#6){++++}, at: lookup_slow+0x49/0x80 fs/namei.c:1687
 #1: 000000000de31ce3 (&fi->mutex){+.+.}, at: fuse_lock_inode+0xba/0xf0 fs/fuse/inode.c:365
2 locks held by getty/13569:
 #0: 00000000d402eb3e (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000d000b4fd (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by syz-executor5/6125:
 #0: 000000005248a2ce (&type->i_mutex_dir_key#6){++++}, at: inode_lock_shared include/linux/fs.h:748 [inline]
 #0: 000000005248a2ce (&type->i_mutex_dir_key#6){++++}, at: lookup_slow+0x49/0x80 fs/namei.c:1687
 #1: 000000000de31ce3 (&fi->mutex){+.+.}, at: fuse_lock_inode+0xba/0xf0 fs/fuse/inode.c:365

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

NMI backtrace for cpu 1
CPU: 1 PID: 792 Comm: khungtaskd Not tainted 4.19.0-rc2+ #220
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+0x1c9/0x2b4 lib/dump_stack.c:113
 nmi_cpu_backtrace.cold.3+0x48/0x88 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x151/0x192 lib/nmi_backtrace.c:62
 arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
 trigger_all_cpu_backtrace include/linux/nmi.h:144 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
 watchdog+0xb39/0x1040 kernel/hung_task.c:265
 kthread+0x35a/0x420 kernel/kthread.c:246
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:413
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0x6/0x10 arch/x86/include/asm/irqflags.h:57

Crashes (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/09/04 02:54 upstream 60c1f89241d4 a4718693 .config console log report ci-upstream-kasan-gce-root
2018/08/30 09:42 upstream ff69279a44e9 6c7e9d3d .config console log report ci-upstream-kasan-gce-root
2018/08/04 21:46 upstream 0b5b1f9a78b5 3476a2df .config console log report ci-upstream-kasan-gce
2018/08/03 04:11 upstream e30cb13c5a09 5b7e23bb .config console log report ci-upstream-kasan-gce
2018/07/24 07:07 upstream d72e90f33aa4 912c93d7 .config console log report ci-upstream-kasan-gce
2018/08/03 12:33 upstream 0585df468e8f cc4f6d0a .config console log report ci-upstream-kasan-gce-386
2018/09/02 21:11 linux-next a880148cb2af a4718693 .config console log report ci-upstream-linux-next-kasan-gce-root
2018/08/18 19:05 linux-next d7857ae43dcc db1858f6 .config console log report ci-upstream-linux-next-kasan-gce-root
2018/08/10 01:49 https://github.com/google/kmsan.git master 0cc51dc9a291 1fb62d58 .config console log report ci-upstream-kmsan-gce
2018/08/09 14:06 https://github.com/google/kmsan.git master 0cc51dc9a291 2eeda842 .config console log report ci-upstream-kmsan-gce
2018/08/08 12:34 https://github.com/google/kmsan.git master b40e5df03d2d ddeb9f8d .config console log report ci-upstream-kmsan-gce
2018/07/22 02:02 https://github.com/google/kmsan.git master d1c2a46a46f6 8cc079c3 .config console log report ci-upstream-kmsan-gce
2018/07/19 16:35 https://github.com/google/kmsan.git master cf8cd3cd03e2 49f35839 .config console log report ci-upstream-kmsan-gce
2018/07/17 19:29 linux-next 1dcbe5f2c615 6d5bd5b5 .config console log report ci-upstream-linux-next-kasan-gce-root
2018/07/15 07:16 linux-next 483d835c8189 92a49505 .config console log report ci-upstream-linux-next-kasan-gce-root
2018/07/14 08:40 https://github.com/google/kmsan.git master 80ecacc456c1 92a49505 .config console log report ci-upstream-kmsan-gce
* Struck through repros no longer work on HEAD.