[v5.15] INFO: task hung in fuse_lookup
12 views
Skip to first unread message
syzbot
Jun 6, 2023, 10:49:44 PM6/6/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d7af3e5ba454 Linux 5.15.115
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e61a7d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc49fb9fb40e8b87
dashboard link: https://syzkaller.appspot.com/bug?extid=e762e7812fed7fbf7dad
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c52779280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/648d6fb5d654/disk-d7af3e5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a693f550ea71/vmlinux-d7af3e5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/09afa713a569/Image-d7af3e5b.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fd20e6de044d/mount_7.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e762e7...@syzkaller.appspotmail.com
INFO: task syz-executor.0:4036 blocked for more than 143 seconds.
Not tainted 5.15.115-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 4036 ppid: 1 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:436
fuse_lookup+0xf0/0x4d4 fs/fuse/dir.c:423
__lookup_slow+0x250/0x388 fs/namei.c:1659
lookup_slow+0x60/0x84 fs/namei.c:1676
walk_component+0x394/0x4cc fs/namei.c:1972
link_path_walk+0x5a0/0xc38
path_openat+0x1e8/0x26f0 fs/namei.c:3668
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.0:4057 blocked for more than 143 seconds.
Not tainted 5.15.115-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 4057 ppid: 4036 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
request_wait_answer fs/fuse/dev.c:411 [inline]
__fuse_request_send fs/fuse/dev.c:430 [inline]
fuse_simple_request+0xea8/0x1758 fs/fuse/dev.c:515
fuse_lookup_name+0x27c/0x6ac fs/fuse/dir.c:383
fuse_lookup+0x13c/0x4d4 fs/fuse/dir.c:424
__lookup_slow+0x250/0x388 fs/namei.c:1659
lookup_slow+0x60/0x84 fs/namei.c:1676
walk_component+0x394/0x4cc fs/namei.c:1972
link_path_walk+0x5a0/0xc38
path_openat+0x1e8/0x26f0 fs/namei.c:3668
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014aa19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3730:
#0: ffff0000d2df9098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a2be2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
2 locks held by syz-executor.0/4036:
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
#1: ffff0000df9d05b8 (&fi->mutex){+.+.}-{3:3}, at: fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:436
2 locks held by syz-executor.0/4057:
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
#1: ffff0000df9d05b8 (&fi->mutex){+.+.}-{3:3}, at: fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:436
=============================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: d7af3e5ba454 Linux 5.15.115
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e61a7d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc49fb9fb40e8b87
dashboard link: https://syzkaller.appspot.com/bug?extid=e762e7812fed7fbf7dad
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c52779280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/648d6fb5d654/disk-d7af3e5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a693f550ea71/vmlinux-d7af3e5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/09afa713a569/Image-d7af3e5b.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fd20e6de044d/mount_7.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e762e7...@syzkaller.appspotmail.com
INFO: task syz-executor.0:4036 blocked for more than 143 seconds.
Not tainted 5.15.115-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 4036 ppid: 1 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:436
fuse_lookup+0xf0/0x4d4 fs/fuse/dir.c:423
__lookup_slow+0x250/0x388 fs/namei.c:1659
lookup_slow+0x60/0x84 fs/namei.c:1676
walk_component+0x394/0x4cc fs/namei.c:1972
link_path_walk+0x5a0/0xc38
path_openat+0x1e8/0x26f0 fs/namei.c:3668
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.0:4057 blocked for more than 143 seconds.
Not tainted 5.15.115-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 4057 ppid: 4036 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
request_wait_answer fs/fuse/dev.c:411 [inline]
__fuse_request_send fs/fuse/dev.c:430 [inline]
fuse_simple_request+0xea8/0x1758 fs/fuse/dev.c:515
fuse_lookup_name+0x27c/0x6ac fs/fuse/dir.c:383
fuse_lookup+0x13c/0x4d4 fs/fuse/dir.c:424
__lookup_slow+0x250/0x388 fs/namei.c:1659
lookup_slow+0x60/0x84 fs/namei.c:1676
walk_component+0x394/0x4cc fs/namei.c:1972
link_path_walk+0x5a0/0xc38
path_openat+0x1e8/0x26f0 fs/namei.c:3668
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014aa19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3730:
#0: ffff0000d2df9098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a2be2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
2 locks held by syz-executor.0/4036:
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
#1: ffff0000df9d05b8 (&fi->mutex){+.+.}-{3:3}, at: fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:436
2 locks held by syz-executor.0/4057:
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
#0: ffff0000df9d0150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
#1: ffff0000df9d05b8 (&fi->mutex){+.+.}-{3:3}, at: fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:436
=============================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Jun 7, 2023, 1:32:22 AM6/7/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 76ba310227d2 Linux 6.1.32
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d81f79280000
kernel config: https://syzkaller.appspot.com/x/.config?x=3d054c5c4a3e2d63
dashboard link: https://syzkaller.appspot.com/bug?extid=840bde9f70b05fb1c05e
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c9e495280000
userspace arch: arm64
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e0c868320bc7/disk-76ba3102.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f7fcc207e1e7/vmlinux-76ba3102.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5ddc172b4acf/Image-76ba3102.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3b765ded753a/mount_7.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
INFO: task syz-executor.0:4291 blocked for more than 143 seconds.
Not tainted 6.1.32-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:0 pid:4291 ppid:1 flags:0x00000001
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6689
__mutex_lock_common+0xbd8/0x21a0 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:468
fuse_lookup+0xf0/0x4b0 fs/fuse/dir.c:432
__lookup_slow+0x250/0x374 fs/namei.c:1685
lookup_slow+0x60/0x84 fs/namei.c:1702
walk_component fs/namei.c:1993 [inline]
link_path_walk+0x830/0xcc8 fs/namei.c:2320
path_openat+0x1c8/0x2548 fs/namei.c:3710
do_filp_open+0x1bc/0x3cc fs/namei.c:3741
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
INFO: task syz-executor.0:4312 blocked for more than 143 seconds.
Not tainted 6.1.32-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:0 pid:4312 ppid:4291 flags:0x00000009
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
request_wait_answer fs/fuse/dev.c:407 [inline]
__fuse_request_send fs/fuse/dev.c:426 [inline]
fuse_simple_request+0xdd8/0x15c0 fs/fuse/dev.c:511
fuse_lookup_name+0x27c/0x6ac fs/fuse/dir.c:392
fuse_lookup+0x13c/0x4b0 fs/fuse/dir.c:433
__lookup_slow+0x250/0x374 fs/namei.c:1685
lookup_slow+0x60/0x84 fs/namei.c:1702
walk_component fs/namei.c:1993 [inline]
link_path_walk+0x830/0xcc8 fs/namei.c:2320
path_openat+0x1c8/0x2548 fs/namei.c:3710
do_filp_open+0x1bc/0x3cc fs/namei.c:3741
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Showing all locks held in the system:
#0: ffff800015794e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffff800015795670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffff800015794ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3981:
#0: ffff0000d8490098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001ba402f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
2 locks held by syz-executor.0/4291:
#0: ffff0000e2a20150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:766 [inline]
#0: ffff0000e2a20150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1701
#1: ffff0000e2a205b8 (&fi->mutex){+.+.}-{3:3}, at: fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:468
2 locks held by syz-executor.0/4312:
#0: ffff0000e2a20150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:766 [inline]
#0: ffff0000e2a20150 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1701
#1: ffff0000e2a205b8 (&fi->mutex){+.+.}-{3:3}, at: fuse_lock_inode+0xd4/0x11c fs/fuse/inode.c:468
Reply all
Reply to author
Forward
0 new messages