[v5.15] WARNING: bad unlock balance in ocfs2_inode_cache_io_unlock

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1126229f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=2f2b61f2e80f27641e4b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2f2b61...@syzkaller.appspotmail.com

ocfs2: Mounting device (7,3) on (node local, slot 0) with ordered data mode.
(syz.3.11,4130,0):ocfs2_read_blocks:240 ERROR: status = -12
=====================================
WARNING: bad unlock balance detected!
5.15.167-syzkaller #0 Not tainted
-------------------------------------
syz.3.11/4130 is trying to release lock (&oi->ip_io_mutex) at:
[<ffff800009e04358>] ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648
but there are no more locks to release!

other info that might help us debug this:
8 locks held by syz.3.11/4130:
#0: ffff0000e80d0460 (sb_writers#11){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000e74f89c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#1: ffff0000e74f89c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
#2: ffff0000e75009c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#2: ffff0000e75009c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: ocfs2_reserve_suballoc_bits+0x164/0x416c fs/ocfs2/suballoc.c:782
#3: ffff0000e74fed88 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#3: ffff0000e74fed88 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{3:3}, at: ocfs2_reserve_suballoc_bits+0x164/0x416c fs/ocfs2/suballoc.c:782
#4: ffff0000e7502648 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#4: ffff0000e7502648 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){+.+.}-{3:3}, at: ocfs2_reserve_local_alloc_bits+0xfc/0x2474 fs/ocfs2/localalloc.c:635
#5: ffff0000e80d0650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_mknod+0xe68/0x24f8 fs/ocfs2/namei.c:359
#6: ffff0000ce4014e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#7: ffff0000d7a7e990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462

stack backtrace:
CPU: 1 PID: 4130 Comm: syz.3.11 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
print_unlock_imbalance_bug+0x250/0x2a4 kernel/locking/lockdep.c:5065
lock_release+0x4b8/0xa1c kernel/locking/lockdep.c:5643
__mutex_unlock_slowpath+0xe0/0x6d4 kernel/locking/mutex.c:851
mutex_unlock+0x8c/0xe0 kernel/locking/mutex.c:536
ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648
ocfs2_metadata_cache_io_unlock+0x6c/0x90 fs/ocfs2/uptodate.c:95
ocfs2_read_blocks+0x1114/0x1628 fs/ocfs2/buffer_head_io.c:394
ocfs2_read_block fs/ocfs2/buffer_head_io.h:52 [inline]
ocfs2_read_group_descriptor fs/ocfs2/suballoc.c:299 [inline]
ocfs2_search_chain+0x274/0x22f0 fs/ocfs2/suballoc.c:1757
ocfs2_claim_suballoc_bits+0xd38/0x1d84 fs/ocfs2/suballoc.c:1930
ocfs2_claim_new_inode+0x2cc/0x7a0 fs/ocfs2/suballoc.c:2210
ocfs2_mknod_locked+0x134/0x2e4 fs/ocfs2/namei.c:633
ocfs2_mknod+0x10b0/0x24f8 fs/ocfs2/namei.c:379
vfs_mknod+0x3c8/0x448 fs/namei.c:3944
do_mknodat+0x3c8/0x694
__do_sys_mknodat fs/namei.c:4022 [inline]
__se_sys_mknodat fs/namei.c:4019 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:4019
__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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
(syz.3.11,4130,0):ocfs2_search_chain:1761 ERROR: status = -12
(syz.3.11,4130,0):ocfs2_search_chain:1871 ERROR: status = -12
(syz.3.11,4130,0):ocfs2_claim_suballoc_bits:1940 ERROR: status = -12
(syz.3.11,4130,1):ocfs2_claim_suballoc_bits:1983 ERROR: status = -12
(syz.3.11,4130,1):ocfs2_claim_new_inode:2216 ERROR: status = -12
(syz.3.11,4130,1):ocfs2_claim_new_inode:2231 ERROR: status = -12
(syz.3.11,4130,1):ocfs2_mknod_locked:637 ERROR: status = -12
(syz.3.11,4130,1):ocfs2_mknod:383 ERROR: status = -12
(syz.3.11,4130,1):ocfs2_mknod:500 ERROR: status = -12


---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=17a4f407980000

kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=2f2b61f2e80f27641e4b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c5c8a9980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1064f407980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/45a1325da365/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2f2b61...@syzkaller.appspotmail.com

ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
(syz-executor308,4015,1):ocfs2_read_blocks:240 ERROR: status = -12

=====================================
WARNING: bad unlock balance detected!
5.15.167-syzkaller #0 Not tainted
-------------------------------------

syz-executor308/4015 is trying to release lock (&oi->ip_io_mutex) at:

[<ffff800009e04358>] ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648
but there are no more locks to release!

other info that might help us debug this:

8 locks held by syz-executor308/4015:
#0: ffff0000cbfca460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000e19289c8 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#1: ffff0000e19289c8 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
#2: ffff0000e19309c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#2: ffff0000e19309c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: ocfs2_reserve_suballoc_bits+0x164/0x416c fs/ocfs2/suballoc.c:782
#3: ffff0000e192ed88 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#3: ffff0000e192ed88 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{3:3}, at: ocfs2_reserve_suballoc_bits+0x164/0x416c fs/ocfs2/suballoc.c:782
#4: ffff0000e1932648 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#4: ffff0000e1932648 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){+.+.}-{3:3}, at: ocfs2_reserve_local_alloc_bits+0xfc/0x2474 fs/ocfs2/localalloc.c:635
#5: ffff0000cbfca650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_mknod+0xe68/0x24f8 fs/ocfs2/namei.c:359
#6: ffff0000da2988e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x45c/0x804 fs/ocfs2/journal.c:352
#7: ffff0000cbfc8990 (jbd2_handle){.+.+}-{0:0}, at: start_this_handle+0xf98/0x12a4 fs/jbd2/transaction.c:462

stack backtrace:
CPU: 1 PID: 4015 Comm: syz-executor308 Not tainted 5.15.167-syzkaller #0

(syz-executor308,4015,1):ocfs2_search_chain:1761 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_search_chain:1871 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_claim_suballoc_bits:1940 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_claim_suballoc_bits:1983 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_claim_new_inode:2216 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_claim_new_inode:2231 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_mknod_locked:637 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_mknod:383 ERROR: status = -12
(syz-executor308,4015,1):ocfs2_mknod:500 ERROR: status = -12


---
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.

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5f55cad62cc9 Linux 6.1.110
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13ca1797980000
kernel config: https://syzkaller.appspot.com/x/.config?x=625d3d5479b9ea13
dashboard link: https://syzkaller.appspot.com/bug?extid=04978ef8a2b125297d95

compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/406d4fabf0c5/disk-5f55cad6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/abc54e64f4c6/vmlinux-5f55cad6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d3b04a9f829/Image-5f55cad6.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+04978e...@syzkaller.appspotmail.com

ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
(syz.1.455,5761,1):ocfs2_read_blocks:240 ERROR: status = -12

=====================================
WARNING: bad unlock balance detected!

6.1.110-syzkaller #0 Not tainted
-------------------------------------
syz.1.455/5761 is trying to release lock (&oi->ip_io_mutex) at:
[<ffff800009ee7c74>] ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648

but there are no more locks to release!

other info that might help us debug this:

8 locks held by syz.1.455/5761:
#0: ffff0000f696c460 (sb_writers#16){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e14ca648 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff0000e14ca648 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3878
#2: ffff0000e14e6d88 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#2: ffff0000e14e6d88 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: ocfs2_reserve_suballoc_bits+0x164/0x4428 fs/ocfs2/suballoc.c:782
#3: ffff0000e14cd108 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#3: ffff0000e14cd108 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#3){+.+.}-{3:3}, at: ocfs2_reserve_suballoc_bits+0x164/0x4428 fs/ocfs2/suballoc.c:782
#4: ffff0000e14e2648 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#4: ffff0000e14e2648 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){+.+.}-{3:3}, at: ocfs2_reserve_local_alloc_bits+0xfc/0x25dc fs/ocfs2/localalloc.c:635
#5: ffff0000f696c650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_mknod+0xe64/0x2560 fs/ocfs2/namei.c:359
#6: ffff0000d44d20e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x3dc/0x73c fs/ocfs2/journal.c:352
#7: ffff0000cd9b2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1118/0x13ac fs/jbd2/transaction.c:461

stack backtrace:
CPU: 1 PID: 5761 Comm: syz.1.455 Not tainted 6.1.110-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call trace:

dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165

__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113

print_unlock_imbalance_bug+0x250/0x2a4 kernel/locking/lockdep.c:5102
lock_release+0x4dc/0xa50 kernel/locking/lockdep.c:5682
__mutex_unlock_slowpath+0xe0/0x6cc kernel/locking/mutex.c:907
mutex_unlock+0x24/0x30 kernel/locking/mutex.c:543

ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648
ocfs2_metadata_cache_io_unlock+0x6c/0x90 fs/ocfs2/uptodate.c:95

ocfs2_read_blocks+0x11d0/0x17e8 fs/ocfs2/buffer_head_io.c:394

ocfs2_read_block fs/ocfs2/buffer_head_io.h:52 [inline]
ocfs2_read_group_descriptor fs/ocfs2/suballoc.c:299 [inline]

ocfs2_search_chain+0x28c/0x239c fs/ocfs2/suballoc.c:1757
ocfs2_claim_suballoc_bits+0xd38/0x1e1c fs/ocfs2/suballoc.c:1930
ocfs2_claim_new_inode+0x2d0/0x798 fs/ocfs2/suballoc.c:2210
ocfs2_mknod_locked+0x134/0x2e4 fs/ocfs2/namei.c:633
ocfs2_mknod+0x10ac/0x2560 fs/ocfs2/namei.c:379
vfs_mknod+0x3c8/0x448 fs/namei.c:3987
do_mknodat+0x3f8/0x610
__do_sys_mknodat fs/namei.c:4065 [inline]
__se_sys_mknodat fs/namei.c:4062 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:4062
__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:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
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:585
(syz.1.455,5761,1):ocfs2_search_chain:1761 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_search_chain:1871 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_claim_suballoc_bits:1940 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_claim_suballoc_bits:1983 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_claim_new_inode:2216 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_claim_new_inode:2231 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_mknod_locked:637 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_mknod:383 ERROR: status = -12
(syz.1.455,5761,1):ocfs2_mknod:500 ERROR: status = -12


---

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: e526b12bf916 Linux 6.1.111
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15a76c27980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7418080a6f941760

dashboard link: https://syzkaller.appspot.com/bug?extid=04978ef8a2b125297d95
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11238e07980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1774b080580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1729a6745b21/disk-e526b12b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f358663fa696/vmlinux-e526b12b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b39a7b8f250/Image-e526b12b.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b9097d19b176/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+04978e...@syzkaller.appspotmail.com

option from the mount to silence this warning.
=======================================================
(syz-executor171,4294,1):ocfs2_read_blocks:240 ERROR: status = -12

=====================================
WARNING: bad unlock balance detected!

6.1.111-syzkaller #0 Not tainted
-------------------------------------
syz-executor171/4294 is trying to release lock (&oi->ip_io_mutex) at:
[<ffff800009ee6b4c>] ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648

but there are no more locks to release!

other info that might help us debug this:

1 lock held by syz-executor171/4294:
#0: ffff0000da0760e0 (&type->s_umount_key#39/1){+.+.}-{3:3}, at: alloc_super+0x1b4/0x824 fs/super.c:228

stack backtrace:
CPU: 1 PID: 4294 Comm: syz-executor171 Not tainted 6.1.111-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
print_unlock_imbalance_bug+0x250/0x2a4 kernel/locking/lockdep.c:5102
lock_release+0x4dc/0xa50 kernel/locking/lockdep.c:5682
__mutex_unlock_slowpath+0xe0/0x6cc kernel/locking/mutex.c:907
mutex_unlock+0x24/0x30 kernel/locking/mutex.c:543
ocfs2_inode_cache_io_unlock+0x20/0x30 fs/ocfs2/inode.c:1648
ocfs2_metadata_cache_io_unlock+0x6c/0x90 fs/ocfs2/uptodate.c:95
ocfs2_read_blocks+0x11d0/0x17e8 fs/ocfs2/buffer_head_io.c:394

ocfs2_map_slot_buffers fs/ocfs2/slot_map.c:385 [inline]
ocfs2_init_slot_info+0x920/0x1300 fs/ocfs2/slot_map.c:424
ocfs2_initialize_super fs/ocfs2/super.c:2274 [inline]
ocfs2_fill_super+0x2894/0x4a0c fs/ocfs2/super.c:994
mount_bdev+0x274/0x370 fs/super.c:1443
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1186
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3051
path_mount+0x590/0xe5c fs/namespace.c:3381
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount fs/namespace.c:3579 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3579

__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:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
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:585

(syz-executor171,4294,1):ocfs2_map_slot_buffers:388 ERROR: status = -12
(syz-executor171,4294,1):ocfs2_init_slot_info:426 ERROR: status = -12
(syz-executor171,4294,1):ocfs2_initialize_super:2276 ERROR: status = -12
(syz-executor171,4294,1):ocfs2_fill_super:1176 ERROR: status = -12


---

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.