[v6.1] WARNING in hfsplus_bnode_create

0 views
Skip to first unread message

syzbot

unread,
Apr 25, 2023, 3:58:00 AM4/25/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: f17b0ab65d17 Linux 6.1.25
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147654a4280000
kernel config: https://syzkaller.appspot.com/x/.config?x=73f7ee8e484b74b7
dashboard link: https://syzkaller.appspot.com/bug?extid=a461be35cc94089b7f93
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/553994c02131/disk-f17b0ab6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c88e4d2795a5/vmlinux-f17b0ab6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d788d429a3a9/Image-f17b0ab6.gz.xz

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

loop1: detected capacity change from 0 to 1024
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 0 PID: 24819 at fs/hfsplus/bnode.c:573 hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
Modules linked in:
CPU: 0 PID: 24819 Comm: syz-executor.1 Not tainted 6.1.25-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
lr : hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
sp : ffff8000304d6a90
x29: ffff8000304d6aa0 x28: dfff800000000000 x27: dfff800000000000
x26: ffff0001146f30f8 x25: dfff800000000000 x24: ffff0000d113c888
x23: 0000000000000000 x22: ffff0001294ba0e0 x21: ffff0001294ba000
x20: 0000000000000000 x19: ffff0000d113c800 x18: 1fffe000368b6b76
x17: ffff80001557d000 x16: ffff8000120dc5fc x15: ffff0001b45b5bbc
x14: 1ffff00002ab00b0 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000001af3d x10: ffff80002247a000 x9 : d92acaaacdd21000
x8 : d92acaaacdd21000 x7 : ffff800008279fb8 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80000aa6b40c
x2 : ffff0001b45b5cd0 x1 : 0000000100000000 x0 : 0000000000000023
Call trace:
hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
hfsplus_bmap_alloc+0x570/0x638 fs/hfsplus/btree.c:415
hfs_btree_inc_height+0xf8/0xa60 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x11c/0xaa0 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x288/0x4ac fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
hfsplus_file_extend+0x390/0x14cc fs/hfsplus/extents.c:461
hfsplus_get_block+0x398/0x1168 fs/hfsplus/extents.c:245
__block_write_begin_int+0x340/0x13b4 fs/buffer.c:1991
__block_write_begin fs/buffer.c:2041 [inline]
block_write_begin fs/buffer.c:2102 [inline]
cont_write_begin+0x5c0/0x7d8 fs/buffer.c:2456
hfsplus_write_begin+0x98/0xe4 fs/hfsplus/inode.c:52
generic_perform_write+0x278/0x55c mm/filemap.c:3754
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3882
generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:3914
call_write_iter include/linux/fs.h:2205 [inline]
aio_write+0x588/0x824 fs/aio.c:1604
io_submit_one+0x824/0x15b8 fs/aio.c:2023
__do_sys_io_submit fs/aio.c:2082 [inline]
__se_sys_io_submit fs/aio.c:2052 [inline]
__arm64_sys_io_submit+0x248/0x3c8 fs/aio.c:2052
__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
irq event stamp: 5642
hardirqs last enabled at (5641): [<ffff80000827a058>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1366 [inline]
hardirqs last enabled at (5641): [<ffff80000827a058>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5000
hardirqs last disabled at (5642): [<ffff8000120d82b4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (4890): [<ffff800008032b74>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (4888): [<ffff800008032b40>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
------------[ cut here ]------------
kernel BUG at fs/hfsplus/bnode.c:618!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 24819 Comm: syz-executor.1 Tainted: G W 6.1.25-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
lr : hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
sp : ffff8000304d6b80
x29: ffff8000304d6b80 x28: dfff800000000000 x27: ffff70000609ad88
x26: 1fffe00025297403 x25: 1fffe0001a227900 x24: ffff0001294ba000
x23: dfff800000000000 x22: ffff0000d113c800 x21: ffff0000d113c880
x20: 0000000000000000 x19: ffff0000d113c800 x18: 1fffe000368b6b76
x17: ffff80001557d000 x16: ffff8000120dc72c x15: ffff0001b45b5bbc
x14: 1ffff00002ab00b0 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003912b x10: ffff80002247a000 x9 : ffff800009074e84
x8 : 000000000003912c x7 : ffff8000089c6e64 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800009074a58
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
hfs_btree_inc_height+0x4fc/0xa60 fs/hfsplus/brec.c:530
hfsplus_brec_insert+0x11c/0xaa0 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x288/0x4ac fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
hfsplus_file_extend+0x390/0x14cc fs/hfsplus/extents.c:461
hfsplus_get_block+0x398/0x1168 fs/hfsplus/extents.c:245
__block_write_begin_int+0x340/0x13b4 fs/buffer.c:1991
__block_write_begin fs/buffer.c:2041 [inline]
block_write_begin fs/buffer.c:2102 [inline]
cont_write_begin+0x5c0/0x7d8 fs/buffer.c:2456
hfsplus_write_begin+0x98/0xe4 fs/hfsplus/inode.c:52
generic_perform_write+0x278/0x55c mm/filemap.c:3754
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3882
generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:3914
call_write_iter include/linux/fs.h:2205 [inline]
aio_write+0x588/0x824 fs/aio.c:1604
io_submit_one+0x824/0x15b8 fs/aio.c:2023
__do_sys_io_submit fs/aio.c:2082 [inline]
__se_sys_io_submit fs/aio.c:2052 [inline]
__arm64_sys_io_submit+0x248/0x3c8 fs/aio.c:2052
__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
Code: aa1403e0 97e3cdbc 17ffffb7 97d206f1 (d4210000)
---[ end trace 0000000000000000 ]---


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

unread,
May 7, 2023, 12:50:05 PM5/7/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: ca48fc16c493 Linux 6.1.27
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14875338280000
kernel config: https://syzkaller.appspot.com/x/.config?x=aea4bb7802570997
dashboard link: https://syzkaller.appspot.com/bug?extid=a461be35cc94089b7f93
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=134d20a2280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1351f114280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ec11c1903c52/disk-ca48fc16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8ce41c1ad391/vmlinux-ca48fc16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/affba5631cad/Image-ca48fc16.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/c63f1d6b2150/mount_0.gz

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

loop0: detected capacity change from 0 to 1024
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4222 at fs/hfsplus/bnode.c:573 hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
Modules linked in:
CPU: 0 PID: 4222 Comm: syz-executor242 Not tainted 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
lr : hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
sp : ffff80001db06cf0
x29: ffff80001db06d00 x28: dfff800000000000 x27: dfff800000000000
x26: ffff0001884a30f8 x25: dfff800000000000 x24: ffff0000c089f288
x23: 0000000000000000 x22: ffff0000d85780e0 x21: ffff0000d8578000
x20: 0000000000000000 x19: ffff0000c089f200 x18: ffff80001db06240
x17: 0000000000000000 x16: ffff8000120e6354 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000001
x11: ff8080000834483c x10: 0000000000000000 x9 : 4bc35f085a66a100
x8 : 4bc35f085a66a100 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001db065f8 x4 : ffff800015672960 x3 : ffff80000aa6d06c
x2 : ffff0001b45b3cd0 x1 : 0000000100000000 x0 : 0000000000000023
Call trace:
hfsplus_bnode_create+0x428/0x4dc fs/hfsplus/bnode.c:572
hfsplus_bmap_alloc+0x570/0x638 fs/hfsplus/btree.c:415
hfs_btree_inc_height+0xf8/0xa60 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x11c/0xaa0 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x288/0x4ac fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
hfsplus_file_extend+0x390/0x14cc fs/hfsplus/extents.c:461
hfsplus_get_block+0x398/0x1168 fs/hfsplus/extents.c:245
__block_write_begin_int+0x340/0x13b4 fs/buffer.c:1991
__block_write_begin fs/buffer.c:2041 [inline]
block_write_begin fs/buffer.c:2102 [inline]
cont_write_begin+0x5c0/0x7d8 fs/buffer.c:2456
hfsplus_write_begin+0x98/0xe4 fs/hfsplus/inode.c:52
generic_perform_write+0x278/0x55c mm/filemap.c:3754
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3882
generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:3914
call_write_iter include/linux/fs.h:2205 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x914 fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__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
irq event stamp: 20982
hardirqs last enabled at (20981): [<ffff80000834278c>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (20982): [<ffff8000120e200c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (20636): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (20636): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (20611): [<ffff80000802a948>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
---[ end trace 0000000000000000 ]---
------------[ cut here ]------------
kernel BUG at fs/hfsplus/bnode.c:618!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4222 Comm: syz-executor242 Tainted: G W 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
lr : hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
sp : ffff80001db06de0
x29: ffff80001db06de0 x28: dfff800000000000 x27: ffff700003b60dd4
x26: 1fffe0001b0af003 x25: 1fffe00018113e40 x24: ffff0000d8578000
x23: dfff800000000000 x22: ffff0000c089f200 x21: ffff0000c089f280
x20: 0000000000000000 x19: ffff0000c089f200 x18: ffff80001db06240
x17: 0000000000000000 x16: ffff8000120e6484 x15: 0000000000000000
x14: 1ffff00002ab20b0 x13: dfff800000000000 x12: 0000000000000001
x11: ff808000090788f4 x10: 0000000000000000 x9 : ffff8000090788f4
x8 : ffff0000c62d8000 x7 : ffff8000089c9408 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff8000090784c8
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
hfs_btree_inc_height+0x4fc/0xa60 fs/hfsplus/brec.c:530
hfsplus_brec_insert+0x11c/0xaa0 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x288/0x4ac fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
hfsplus_file_extend+0x390/0x14cc fs/hfsplus/extents.c:461
hfsplus_get_block+0x398/0x1168 fs/hfsplus/extents.c:245
__block_write_begin_int+0x340/0x13b4 fs/buffer.c:1991
__block_write_begin fs/buffer.c:2041 [inline]
block_write_begin fs/buffer.c:2102 [inline]
cont_write_begin+0x5c0/0x7d8 fs/buffer.c:2456
hfsplus_write_begin+0x98/0xe4 fs/hfsplus/inode.c:52
generic_perform_write+0x278/0x55c mm/filemap.c:3754
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3882
generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:3914
call_write_iter include/linux/fs.h:2205 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x914 fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__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
Code: aa1403e0 97e3c737 17ffffb7 97d2009d (d4210000)
---[ end trace 0000000000000000 ]---


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

unread,
May 13, 2023, 3:31:43 PM5/13/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b0ece631f84a Linux 5.15.111
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14d2eb56280000
kernel config: https://syzkaller.appspot.com/x/.config?x=db3750b003ff805e
dashboard link: https://syzkaller.appspot.com/bug?extid=b9a11951980cf86e1899
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=17a27d7c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16700e16280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eded75b6c3f9/disk-b0ece631.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/20e5ae802010/vmlinux-b0ece631.xz
kernel image: https://storage.googleapis.com/syzbot-assets/05d665c869f3/Image-b0ece631.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b1da1a2057fb/mount_0.gz

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

loop0: detected capacity change from 0 to 1024
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3968 at fs/hfsplus/bnode.c:584 hfsplus_bnode_create+0x428/0x4ec fs/hfsplus/bnode.c:583
Modules linked in:
CPU: 1 PID: 3968 Comm: syz-executor870 Not tainted 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_bnode_create+0x428/0x4ec fs/hfsplus/bnode.c:583
lr : hfsplus_bnode_create+0x428/0x4ec fs/hfsplus/bnode.c:583
sp : ffff80001cdb6c70
x29: ffff80001cdb6c80 x28: ffff0000ddcd60f8 x27: ffff0000ddcd6000
x26: 00000000000000f8 x25: dfff800000000000 x24: 0000000000000000
x23: 0000000000000000 x22: ffff0000c9a440e0 x21: ffff0000c9a44000
x20: 0000000000000000 x19: ffff0000c0f7fc00 x18: 0000000000000001
x17: ff808000083359dc x16: ffff800011948074 x15: ffff8000083359dc
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000832c484 x10: 0000000000000000 x9 : 825ef17445ee0200
x8 : 825ef17445ee0200 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001cdb63d8 x4 : ffff8000149afce0 x3 : ffff80000a9525e0
x2 : ffff0001b481ed10 x1 : 0000000100000000 x0 : 0000000000000023
Call trace:
hfsplus_bnode_create+0x428/0x4ec fs/hfsplus/bnode.c:583
hfsplus_bmap_alloc+0x5a4/0x698 fs/hfsplus/btree.c:414
hfs_btree_inc_height+0xf8/0xa60 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x11c/0xaa0 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x288/0x4bc fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
hfsplus_file_extend+0x390/0x14e0 fs/hfsplus/extents.c:461
hfsplus_get_block+0x398/0x1194 fs/hfsplus/extents.c:245
__block_write_begin_int+0x3ec/0x1608 fs/buffer.c:2012
__block_write_begin fs/buffer.c:2062 [inline]
block_write_begin fs/buffer.c:2122 [inline]
cont_write_begin+0x538/0x710 fs/buffer.c:2471
hfsplus_write_begin+0xa8/0xf8 fs/hfsplus/inode.c:53
generic_perform_write+0x24c/0x520 mm/filemap.c:3776
__generic_file_write_iter+0x230/0x454 mm/filemap.c:3903
generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3935
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x87c/0xb3c fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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
irq event stamp: 18202
hardirqs last enabled at (18201): [<ffff80000832a61c>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (18202): [<ffff800011943708>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (17038): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (17038): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (16663): [<ffff8000081b573c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (16663): [<ffff8000081b573c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (16663): [<ffff8000081b573c>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 67bd52ab03f1bb8b ]---
------------[ cut here ]------------
kernel BUG at fs/hfsplus/bnode.c:631!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 3968 Comm: syz-executor870 Tainted: G W 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_bnode_put+0x588/0x594 fs/hfsplus/bnode.c:631
lr : hfsplus_bnode_put+0x588/0x594 fs/hfsplus/bnode.c:631
sp : ffff80001cdb6d80
x29: ffff80001cdb6d80 x28: dfff800000000000 x27: ffff7000039b6dc8
x26: 1fffe00019348803 x25: ffff0000c9a44000 x24: 1fffe000181eff80
x23: dfff800000000000 x22: ffff0000c0f7fc00 x21: ffff0000c0f7fc80
x20: 0000000000000000 x19: ffff0000c0f7fc00 x18: 0000000000000001
x17: ff808000083359dc x16: ffff800011948204 x15: ffff8000083359dc
x14: 1ffff0000291a06a x13: ffffffffffffffff x12: 0000000000000000
x11: ff80800008fafdd0 x10: 0000000000000000 x9 : ffff800008fafdd0
x8 : ffff0000d8e99b40 x7 : ffff800008914708 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800008faf8a4
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_bnode_put+0x588/0x594 fs/hfsplus/bnode.c:631
hfs_btree_inc_height+0x4fc/0xa60 fs/hfsplus/brec.c:530
hfsplus_brec_insert+0x11c/0xaa0 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x288/0x4bc fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
hfsplus_file_extend+0x390/0x14e0 fs/hfsplus/extents.c:461
hfsplus_get_block+0x398/0x1194 fs/hfsplus/extents.c:245
__block_write_begin_int+0x3ec/0x1608 fs/buffer.c:2012
__block_write_begin fs/buffer.c:2062 [inline]
block_write_begin fs/buffer.c:2122 [inline]
cont_write_begin+0x538/0x710 fs/buffer.c:2471
hfsplus_write_begin+0xa8/0xf8 fs/hfsplus/inode.c:53
generic_perform_write+0x24c/0x520 mm/filemap.c:3776
__generic_file_write_iter+0x230/0x454 mm/filemap.c:3903
generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3935
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x87c/0xb3c fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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
Code: aa1403e0 97e45cf7 17ffff77 97d44af2 (d4210000)
---[ end trace 67bd52ab03f1bb8c ]---


---
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
Reply all
Reply to author
Forward
0 new messages