WARNING in dbAllocDmap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9d5c0b3a8e1a Linux 4.14.295
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d633a8880000
kernel config: https://syzkaller.appspot.com/x/.config?x=746c079015a92425
dashboard link: https://syzkaller.appspot.com/bug?extid=d484b2ec23e63cf055db
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10444574880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105d32f4880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed6fcf5895a2/disk-9d5c0b3a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/341aa3534116/vmlinux-9d5c0b3a.xz

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

DEBUG_LOCKS_WARN_ON(__owner_task(owner) != current)
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7999 at kernel/locking/mutex.c:1032 __mutex_unlock_slowpath+0x75c/0x770 kernel/locking/mutex.c:1032
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 7999 Comm: syz-executor182 Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:__mutex_unlock_slowpath+0x75c/0x770 kernel/locking/mutex.c:1032
RSP: 0018:ffff888094b9f6b8 EFLAGS: 00010282
RAX: 0000000000000033 RBX: ffff8880b2c341bf RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffffed1012973ecd
RBP: ffff8880b39d52d0 R08: 0000000000000033 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880b2c341c0 R12: ffffffff8becddc0
R13: 1ffff11012973edb R14: ffff888094b9f6f8 R15: 0000000000000003
dbAllocDmap+0x5f/0x100 fs/jfs/jfs_dmap.c:2080
dbAllocNext+0x2ad/0x370 fs/jfs/jfs_dmap.c:1233
dbAlloc+0x31d/0x980 fs/jfs/jfs_dmap.c:799
extBalloc fs/jfs/jfs_extent.c:531 [inline]
extAlloc+0x478/0xc20 fs/jfs/jfs_extent.c:138
jfs_get_block+0x1be/0x950 fs/jfs/inode.c:259
nobh_write_begin+0x368/0xc10 fs/buffer.c:2676
jfs_write_begin+0x3e/0x190 fs/jfs/inode.c:324
generic_perform_write+0x1c9/0x420 mm/filemap.c:3055
__generic_file_write_iter+0x227/0x590 mm/filemap.c:3180
generic_file_write_iter+0x36f/0x650 mm/filemap.c:3208
call_write_iter include/linux/fs.h:1780 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fb17800ce69
RSP: 002b:00007ffd21fe54b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fb17800ce69
RDX: 000000000208e24b RSI: 0000000020000040 RDI: 0000000000000003
RBP: 00007fb177fcc6d0 R08: 0000000000000000 R09: 00007fb177fcc6d0
R10: 000055555632d2c0 R11: 0000000000000246 R12: 0000000200000004
R13: 0000000000000000 R14: 00080000000000f8 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches