[hfsplus?] WARNING in hfsplus_cat_write_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 97205fccccdc Linux 4.14.303
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1264a789480000
kernel config: https://syzkaller.appspot.com/x/.config?x=9082325d51b8e29e
dashboard link: https://syzkaller.appspot.com/bug?extid=f416df40b0f792b85eed
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=123b0589480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120eb346480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/743935faa88a/disk-97205fcc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c24286de77a6/vmlinux-97205fcc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a69348a09157/bzImage-97205fcc.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/bea7e5baf628/mount_0.gz

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

IPVS: ftp: loaded support on port[0] = 21
------------[ cut here ]------------
WARNING: CPU: 0 PID: 34 at fs/hfsplus/inode.c:593 hfsplus_cat_write_inode+0x6e3/0x7d0 fs/hfsplus/inode.c:593
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 34 Comm: kworker/u4:2 Not tainted 4.14.303-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Workqueue: writeback wb_workfn (flush-7:0)
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:967
RIP: 0010:hfsplus_cat_write_inode+0x6e3/0x7d0 fs/hfsplus/inode.c:593
RSP: 0018:ffff8880b56b7628 EFLAGS: 00010297
RAX: ffff8880b565e1c0 RBX: 1ffff11016ad6ec7 RCX: 1ffff11016ad6e57
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8880b56b7698
RBP: ffff8880b2ebb418 R08: ffff8880b56b7208 R09: ffffed10166dbd0a
R10: ffff8880b36de857 R11: ffff8880b565e1c0 R12: ffff8880b2ebb418
R13: 0000000000000000 R14: ffff8880b2ebb298 R15: ffff8880b56b7668
hfsplus_write_inode fs/hfsplus/super.c:159 [inline]
hfsplus_write_inode+0x6b/0x410 fs/hfsplus/super.c:146
write_inode fs/fs-writeback.c:1241 [inline]
__writeback_single_inode+0x6a4/0x1010 fs/fs-writeback.c:1439
writeback_sb_inodes+0x48b/0xd30 fs/fs-writeback.c:1645
wb_writeback+0x243/0xb80 fs/fs-writeback.c:1820
wb_do_writeback fs/fs-writeback.c:1952 [inline]
wb_workfn+0x2bd/0xf50 fs/fs-writeback.c:1988
process_one_work+0x793/0x14a0 kernel/workqueue.c:2117
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406
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