[v6.1] kernel BUG in hfsplus_bnode_put
0 views
Skip to first unread message
syzbot
Jun 17, 2023, 7:52:56 AM6/17/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1527f2cf280000
kernel config: https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link: https://syzkaller.appspot.com/bug?extid=40bef8b3d36fddf962ca
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=15799287280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1320daef280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/8e8fc60cc797/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+40bef8...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 1024
------------[ cut here ]------------
kernel BUG at fs/hfsplus/bnode.c:618!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4825 Comm: syz-executor351 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/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 : ffff80001e3672a0
x29: ffff80001e3672a0 x28: dfff800000000000 x27: 00000000000000f8
x26: ffff0000e352b0f8 x25: 1fffe000186b3240 x24: ffff0000dbe3a000
x23: dfff800000000000 x22: 1ffff00003c6ce64 x21: ffff0000c3599280
x20: 0000000000000000 x19: ffff0000c3599200 x18: 1fffe000368b9f76
x17: ffff8000155bd000 x16: ffff80000825f9d8 x15: ffff800008a6912c
x14: 1ffff00002ab80b0 x13: dfff800000000000 x12: 0000000000000001
x11: ff8080000907c744 x10: 0000000000000000 x9 : ffff80000907c744
x8 : ffff0000d450b780 x7 : ffff800008af6e54 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000907c318
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
hfsplus_bmap_alloc+0x564/0x638 fs/hfsplus/btree.c:414
hfs_bnode_split+0xcc/0xd88 fs/hfsplus/brec.c:245
hfsplus_brec_insert+0x2d4/0xaa0 fs/hfsplus/brec.c:100
hfsplus_create_cat+0xa68/0x1330 fs/hfsplus/catalog.c:308
hfsplus_mknod+0x14c/0x268 fs/hfsplus/dir.c:494
hfsplus_create+0x38/0x4c fs/hfsplus/dir.c:523
vfs_create+0x2cc/0x434 fs/namei.c:3115
do_mknodat+0x314/0x674 fs/namei.c:3965
__do_sys_mknodat fs/namei.c:3993 [inline]
__se_sys_mknodat fs/namei.c:3990 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:3990
__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 97e3c242 17ffffb7 97d1f711 (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.
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
syzbot found the following issue on:
HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1527f2cf280000
kernel config: https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link: https://syzkaller.appspot.com/bug?extid=40bef8b3d36fddf962ca
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=15799287280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1320daef280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/8e8fc60cc797/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+40bef8...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 1024
------------[ cut here ]------------
kernel BUG at fs/hfsplus/bnode.c:618!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4825 Comm: syz-executor351 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/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 : ffff80001e3672a0
x29: ffff80001e3672a0 x28: dfff800000000000 x27: 00000000000000f8
x26: ffff0000e352b0f8 x25: 1fffe000186b3240 x24: ffff0000dbe3a000
x23: dfff800000000000 x22: 1ffff00003c6ce64 x21: ffff0000c3599280
x20: 0000000000000000 x19: ffff0000c3599200 x18: 1fffe000368b9f76
x17: ffff8000155bd000 x16: ffff80000825f9d8 x15: ffff800008a6912c
x14: 1ffff00002ab80b0 x13: dfff800000000000 x12: 0000000000000001
x11: ff8080000907c744 x10: 0000000000000000 x9 : ffff80000907c744
x8 : ffff0000d450b780 x7 : ffff800008af6e54 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000907c318
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_bnode_put+0x488/0x494 fs/hfsplus/bnode.c:618
hfsplus_bmap_alloc+0x564/0x638 fs/hfsplus/btree.c:414
hfs_bnode_split+0xcc/0xd88 fs/hfsplus/brec.c:245
hfsplus_brec_insert+0x2d4/0xaa0 fs/hfsplus/brec.c:100
hfsplus_create_cat+0xa68/0x1330 fs/hfsplus/catalog.c:308
hfsplus_mknod+0x14c/0x268 fs/hfsplus/dir.c:494
hfsplus_create+0x38/0x4c fs/hfsplus/dir.c:523
vfs_create+0x2cc/0x434 fs/namei.c:3115
do_mknodat+0x314/0x674 fs/namei.c:3965
__do_sys_mknodat fs/namei.c:3993 [inline]
__se_sys_mknodat fs/namei.c:3990 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:3990
__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 97e3c242 17ffffb7 97d1f711 (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.
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
syzbot
Jun 17, 2023, 8:22:49 AM6/17/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 471e639e59d1 Linux 5.15.117
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14324b17280000
kernel config: https://syzkaller.appspot.com/x/.config?x=eeb4064efec7aa39
dashboard link: https://syzkaller.appspot.com/bug?extid=61d25576dc01ec558bb4
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=12fc386b280000
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a79d17280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2e7359ecba67/disk-471e639e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef6d17e44bc3/vmlinux-471e639e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/99b68dbd7e00/Image-471e639e.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/665e4adb969d/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
kernel BUG at fs/hfsplus/bnode.c:631!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 417 Comm: kworker/u4:5 Not tainted 5.15.117-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Workqueue: writeback wb_workfn (flush-7:0)
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 : ffff80001d007240
x29: ffff80001d007240 x28: 1fffe0001918fe93 x27: ffff0000c8ace000
x26: dfff800000000000 x25: ffff0000c9d92000 x24: 1fffe000181fa840
x23: dfff800000000000 x22: 0000000000000100 x21: ffff0000c0fd4280
x20: 0000000000000000 x19: ffff0000c0fd4200 x18: 0000000000000000
x17: ff80800008faecf0 x16: ffff8000119534fc x15: ffff800008faecf0
x14: 1ffff0000291e06a x13: ffffffffffffffff x12: 0000000000000000
x11: ff80800008faf714 x10: 0000000000000000 x9 : ffff800008faf714
x8 : ffff0000c7f9b680 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff800008faf1e8
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_bnode_put+0x588/0x594 fs/hfsplus/bnode.c:631
Call trace:
hfsplus_btree_write+0x2cc/0x6d4 fs/hfsplus/btree.c:308
hfsplus_system_write_inode fs/hfsplus/super.c:136 [inline]
hfsplus_write_inode+0x3a4/0x4ec fs/hfsplus/super.c:162
write_inode fs/fs-writeback.c:1478 [inline]
__writeback_single_inode+0x584/0x13a4 fs/fs-writeback.c:1683
writeback_sb_inodes+0x94c/0x1620 fs/fs-writeback.c:1908
wb_writeback+0x3fc/0xfc8 fs/fs-writeback.c:2082
wb_do_writeback fs/fs-writeback.c:2225 [inline]
wb_workfn+0x3a4/0x1070 fs/fs-writeback.c:2266
process_one_work+0x790/0x11b8 kernel/workqueue.c:2307
worker_thread+0x910/0x1034 kernel/workqueue.c:2454
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: aa1403e0 97e46085 17ffff77 97d44e7b (d4210000)
---[ end trace 814c451ac9864a98 ]---
Reply all
Reply to author
Forward
0 new messages