syzbot


INFO: task hung in fuse_reverse_inval_entry

Status: fixed on 2019/11/11 16:48
Subsystems: fuse
[Documentation on labels]
Reported-by: syzbot+bb6d800770577a083f8c@syzkaller.appspotmail.com
Fix commit: c59fd85e4fd0 fuse: change interrupt requests allocation algorithm
First crash: 2111d, last: 2088d
Fix bisection: fixed by (bisect log) :
commit c59fd85e4fd07fdf0ab523a5e9734f5338d6aa19
Author: Kirill Tkhai <ktkhai@virtuozzo.com>
Date: Tue Sep 11 10:11:56 2018 +0000

  fuse: change interrupt requests allocation algorithm

  
Discussions (3)
Title Replies (including bot) Last reply
INFO: task hung in fuse_reverse_inval_entry 14 (16) 2019/11/07 13:42
Reminder: 5 open syzbot bugs in "fs/fuse" subsystem 1 (1) 2019/07/24 02:32
Reminder: 5 open syzbot bugs in "fs/fuse" subsystem 1 (1) 2019/07/02 05:26
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in fuse_reverse_inval_entry (2) fuse 3 1194d 1212d 0/26 auto-closed as invalid on 2021/04/15 03:59
linux-4.19 INFO: task hung in fuse_reverse_inval_entry C error 2 859d 960d 0/1 upstream: reported C repro on 2021/09/05 19:48
linux-4.14 INFO: task hung in fuse_reverse_inval_entry C 1 428d 851d 0/1 upstream: reported C repro on 2021/12/23 18:36
upstream INFO: task hung in fuse_reverse_inval_entry (4) fuse 1 324d 324d 0/26 auto-obsoleted due to no activity on 2023/09/01 17:45
android-49 INFO: task hung in fuse_reverse_inval_entry C 3 2091d 1836d 0/3 public: reported C repro on 2019/04/14 08:51
upstream INFO: task hung in fuse_reverse_inval_entry (5) fuse 1 230d 230d 0/26 auto-obsoleted due to no activity on 2023/12/04 21:33
upstream INFO: task hung in fuse_reverse_inval_entry (3) fuse 1 500d 500d 0/26 auto-obsoleted due to no activity on 2023/04/10 13:00

Sample crash report:
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
INFO: task syz-executor842:4559 blocked for more than 140 seconds.
      Not tainted 4.18.0-rc6+ #160
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor842 D23528  4559   4556 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2853 [inline]
 __schedule+0x87c/0x1ed0 kernel/sched/core.c:3501
 schedule+0xfb/0x450 kernel/sched/core.c:3545
 __rwsem_down_write_failed_common+0x95d/0x1630 kernel/locking/rwsem-xadd.c:566
 rwsem_down_write_failed+0xe/0x10 kernel/locking/rwsem-xadd.c:595
 call_rwsem_down_write_failed+0x17/0x30 arch/x86/lib/rwsem.S:117
 __down_write arch/x86/include/asm/rwsem.h:142 [inline]
 down_write+0xaa/0x130 kernel/locking/rwsem.c:72
 inode_lock include/linux/fs.h:715 [inline]
 fuse_reverse_inval_entry+0xae/0x6d0 fs/fuse/dir.c:969
 fuse_notify_inval_entry fs/fuse/dev.c:1491 [inline]
 fuse_notify fs/fuse/dev.c:1764 [inline]
 fuse_dev_do_write+0x2b97/0x3700 fs/fuse/dev.c:1848
 fuse_dev_write+0x19a/0x240 fs/fuse/dev.c:1928
 call_write_iter include/linux/fs.h:1793 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x6c6/0x9f0 fs/read_write.c:487
 vfs_write+0x1f8/0x560 fs/read_write.c:549
 ksys_write+0x101/0x260 fs/read_write.c:598
 __do_sys_write fs/read_write.c:610 [inline]
 __se_sys_write fs/read_write.c:607 [inline]
 __x64_sys_write+0x73/0xb0 fs/read_write.c:607
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x445869
Code: Bad RIP value.
RSP: 002b:00007ffa2ef7fda8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000006dac24 RCX: 0000000000445869
RDX: 0000000000000029 RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00000000006dac20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0030656c69662f2e
R13: 64695f70756f7267 R14: 2f30656c69662f2e R15: 0000000000000001
INFO: task syz-executor842:4560 blocked for more than 140 seconds.
      Not tainted 4.18.0-rc6+ #160
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor842 D26008  4560   4556 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2853 [inline]
 __schedule+0x87c/0x1ed0 kernel/sched/core.c:3501
 schedule+0xfb/0x450 kernel/sched/core.c:3545
 request_wait_answer+0x4c8/0x920 fs/fuse/dev.c:463
 __fuse_request_send+0x12a/0x1d0 fs/fuse/dev.c:483
 fuse_request_send+0x62/0xa0 fs/fuse/dev.c:496
 fuse_simple_request+0x33d/0x730 fs/fuse/dev.c:554
 fuse_lookup_name+0x3ee/0x830 fs/fuse/dir.c:323
 fuse_lookup+0xf9/0x4c0 fs/fuse/dir.c:360
 __lookup_hash+0x12e/0x190 fs/namei.c:1505
 filename_create+0x1e5/0x5b0 fs/namei.c:3646
 user_path_create fs/namei.c:3703 [inline]
 do_mkdirat+0xda/0x310 fs/namei.c:3842
 __do_sys_mkdirat fs/namei.c:3861 [inline]
 __se_sys_mkdirat fs/namei.c:3859 [inline]
 __x64_sys_mkdirat+0x76/0xb0 fs/namei.c:3859
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x445869
Code: Bad RIP value.
RSP: 002b:00007ffa2ef5eda8 EFLAGS: 00000297 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00000000006dac3c RCX: 0000000000445869
RDX: 0000000000000000 RSI: 0000000020000500 RDI: 00000000ffffff9c
RBP: 00000000006dac38 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000297 R12: 0030656c69662f2e
R13: 64695f70756f7267 R14: 2f30656c69662f2e R15: 0000000000000001

Showing all locks held in the system:
1 lock held by khungtaskd/901:
 #0: (____ptrval____) (rcu_read_lock){....}, at: debug_show_all_locks+0xd0/0x428 kernel/locking/lockdep.c:4461
1 lock held by rsyslogd/4441:
 #0: (____ptrval____) (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x1bb/0x200 fs/file.c:766
2 locks held by getty/4531:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4532:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4533:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4534:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4535:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4536:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4537:
 #0: (____ptrval____) (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1: (____ptrval____) (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by syz-executor842/4559:
 #0: (____ptrval____) (&fc->killsb){.+.+}, at: fuse_notify_inval_entry fs/fuse/dev.c:1488 [inline]
 #0: (____ptrval____) (&fc->killsb){.+.+}, at: fuse_notify fs/fuse/dev.c:1764 [inline]
 #0: (____ptrval____) (&fc->killsb){.+.+}, at: fuse_dev_do_write+0x2b2d/0x3700 fs/fuse/dev.c:1848
 #1: (____ptrval____) (&type->i_mutex_dir_key#4){+.+.}, at: inode_lock include/linux/fs.h:715 [inline]
 #1: (____ptrval____) (&type->i_mutex_dir_key#4){+.+.}, at: fuse_reverse_inval_entry+0xae/0x6d0 fs/fuse/dir.c:969
3 locks held by syz-executor842/4560:
 #0: (____ptrval____) (sb_writers#9){.+.+}, at: sb_start_write include/linux/fs.h:1554 [inline]
 #0: (____ptrval____) (sb_writers#9){.+.+}, at: mnt_want_write+0x3f/0xc0 fs/namespace.c:386
 #1: (____ptrval____) (&type->i_mutex_dir_key#3/1){+.+.}, at: inode_lock_nested include/linux/fs.h:750 [inline]
 #1: (____ptrval____) (&type->i_mutex_dir_key#3/1){+.+.}, at: filename_create+0x1b2/0x5b0 fs/namei.c:3645
 #2: (____ptrval____) (&fi->mutex){+.+.}, at: fuse_lock_inode+0xaf/0xe0 fs/fuse/inode.c:363

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

NMI backtrace for cpu 1
CPU: 1 PID: 901 Comm: khungtaskd Not tainted 4.18.0-rc6+ #160
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.4+0x19/0xce lib/nmi_backtrace.c:103
 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:138 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:196 [inline]
 watchdog+0x9c4/0xf80 kernel/hung_task.c:252
 kthread+0x345/0x410 kernel/kthread.c:246
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:412
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:54

Crashes (23):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/07/23 03:57 upstream d72e90f33aa4 8cc079c3 .config console log report syz C ci-upstream-kasan-gce-root
2018/07/22 10:01 upstream 490fc053865c 8cc079c3 .config console log report syz C ci-upstream-kasan-gce
2018/07/22 22:51 linux-next 89cf55353308 8cc079c3 .config console log report syz C ci-upstream-linux-next-kasan-gce-root
2018/07/22 07:26 https://github.com/google/kmsan.git master d1c2a46a46f6 8cc079c3 .config console log report syz C ci-upstream-kmsan-gce
2018/07/22 09:05 upstream 490fc053865c 8cc079c3 .config console log report syz ci-upstream-kasan-gce-386
2018/08/05 02:20 upstream 60f5a2173632 3476a2df .config console log report ci-upstream-kasan-gce-root
2018/08/04 20:17 upstream 0b5b1f9a78b5 3476a2df .config console log report ci-upstream-kasan-gce
2018/08/04 13:50 upstream 0b5b1f9a78b5 df7f6947 .config console log report ci-upstream-kasan-gce
2018/08/04 13:41 upstream 0b5b1f9a78b5 df7f6947 .config console log report ci-upstream-kasan-gce
2018/08/03 01:55 upstream e30cb13c5a09 5b7e23bb .config console log report ci-upstream-kasan-gce
2018/08/02 19:30 upstream e30cb13c5a09 5b7e23bb .config console log report ci-upstream-kasan-gce-root
2018/08/02 16:52 upstream 6b4703768268 0a7cf4ec .config console log report ci-upstream-kasan-gce
2018/08/02 07:28 upstream 6b4703768268 0a7cf4ec .config console log report ci-upstream-kasan-gce
2018/07/30 20:02 upstream acb1872577b3 1a381291 .config console log report ci-upstream-kasan-gce-root
2018/07/30 12:50 upstream acb1872577b3 1a381291 .config console log report ci-upstream-kasan-gce
2018/07/29 18:06 upstream a26fb01c2879 0824d7a1 .config console log report ci-upstream-kasan-gce
2018/07/15 16:46 upstream 37b5dca2898d 92a49505 .config console log report ci-upstream-kasan-gce
2018/07/12 18:34 upstream c25c74b7476e 06c33b3a .config console log report ci-upstream-kasan-gce
2018/07/31 23:34 upstream c1d61e7fe376 1477993e .config console log report ci-upstream-kasan-gce-386
2018/07/21 20:44 upstream 48e5aee81f32 8cc079c3 .config console log report ci-upstream-kasan-gce-386
2018/08/04 17:59 linux-next 116b181bb646 3476a2df .config console log report ci-upstream-linux-next-kasan-gce-root
2018/07/22 04:47 https://github.com/google/kmsan.git master d1c2a46a46f6 8cc079c3 .config console log report ci-upstream-kmsan-gce
2018/07/16 00:29 linux-next 483d835c8189 92a49505 .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.