kernel BUG in hfs_write_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126d6b55880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=18d7841cd16056041b58
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=173ce553880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127013c5880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6de175f9dc0d/mount_0.gz

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

IPVS: ftp: loaded support on port[0] = 21
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:441!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3602 Comm: kworker/u4:5 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: writeback wb_workfn (flush-7:0)
RIP: 0010:hfs_write_inode+0x4f2/0x930 fs/hfs/inode.c:441
Code: ae 7d 88 4c 89 ef e8 ed f7 63 ff 49 83 fd 03 0f 84 95 00 00 00 49 83 fd 04 74 11 49 83 fd 02 0f 84 ed fb ff ff e8 1e f6 63 ff <0f> 0b e8 17 f6 63 ff 48 8d 7d 28 48 b8 00 00 00 00 00 fc ff df 48
RSP: 0018:ffff8880a883f7b8 EFLAGS: 00010293
RAX: ffff8880a88ec300 RBX: 1ffff11015107ef9 RCX: ffffffff81fe8f33
RDX: 0000000000000000 RSI: ffffffff81fe8f52 RDI: 0000000000000007
RBP: ffff888095bcc700 R08: 0000000000000000 R09: 0000000000000004
R10: 0000000000000007 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff887dcd20 R15: ffff888095bcc728
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f14f67a8a8 CR3: 00000000a9538000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
write_inode fs/fs-writeback.c:1244 [inline]
__writeback_single_inode+0x733/0x11d0 fs/fs-writeback.c:1442
writeback_sb_inodes+0x537/0xef0 fs/fs-writeback.c:1647
wb_writeback+0x28d/0xcc0 fs/fs-writeback.c:1820
wb_do_writeback fs/fs-writeback.c:1965 [inline]
wb_workfn+0x29b/0x1250 fs/fs-writeback.c:2006
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace beb4931e7add733d ]---
RIP: 0010:hfs_write_inode+0x4f2/0x930 fs/hfs/inode.c:441
Code: ae 7d 88 4c 89 ef e8 ed f7 63 ff 49 83 fd 03 0f 84 95 00 00 00 49 83 fd 04 74 11 49 83 fd 02 0f 84 ed fb ff ff e8 1e f6 63 ff <0f> 0b e8 17 f6 63 ff 48 8d 7d 28 48 b8 00 00 00 00 00 fc ff df 48
RSP: 0018:ffff8880a883f7b8 EFLAGS: 00010293
RAX: ffff8880a88ec300 RBX: 1ffff11015107ef9 RCX: ffffffff81fe8f33
RDX: 0000000000000000 RSI: ffffffff81fe8f52 RDI: 0000000000000007
RBP: ffff888095bcc700 R08: 0000000000000000 R09: 0000000000000004
R10: 0000000000000007 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff887dcd20 R15: ffff888095bcc728
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f14f67a8a8 CR3: 00000000a9538000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 179ef7fe8677 Linux 4.14.300
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d61c4d880000
kernel config: https://syzkaller.appspot.com/x/.config?x=aa85f51ec321d5a9
dashboard link: https://syzkaller.appspot.com/bug?extid=5d3fe841cac4d3ad9b25

compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1735a6f5880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156d67ad880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d311ef57b59a/disk-179ef7fe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/25bf5d729f69/vmlinux-179ef7fe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/db9b96571e69/bzImage-179ef7fe.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/cd302cee6143/mount_0.gz

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

Reported-by: syzbot+5d3fe8...@syzkaller.appspotmail.com

IPVS: ftp: loaded support on port[0] = 21
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:441!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN

Modules linked in:
CPU: 1 PID: 34 Comm: kworker/u4:2 Not tainted 4.14.300-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: writeback wb_workfn (flush-7:0)

task: ffff8880b56a81c0 task.stack: ffff8880b56b0000
RIP: 0010:hfs_write_inode+0x44c/0x860 fs/hfs/inode.c:441
RSP: 0018:ffff8880b56b7870 EFLAGS: 00010297
RAX: ffff8880b56a81c0 RBX: 1ffff11016ad6f10 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880b56b7ab0 RDI: ffff888095a56740
RBP: ffff888095a56700 R08: ffffffff8b9acbe0 R09: 0000000000000002
R10: 0000000000000000 R11: ffff8880b56a81c0 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff879b7ea0 R15: ffff888095a56728
FS: 0000000000000000(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007fffc7c66c18 CR3: 000000009db74000 CR4: 00000000003406e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:

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
Code: 41 5d 41 5e 41 5f c3 e8 13 44 7f ff 49 83 fd 03 0f 84 95 00 00 00 49 83 fd 04 74 11 49 83 fd 02 0f 84 69 fc ff ff e8 f4 43 7f ff <0f> 0b e8 ed 43 7f ff 48 8d 7d 28 48 b8 00 00 00 00 00 fc ff df
RIP: hfs_write_inode+0x44c/0x860 fs/hfs/inode.c:441 RSP: ffff8880b56b7870
---[ end trace 4d08f7a4ff7538a1 ]---