WARNING in hfsplus_bnode_create
4 views
Skip to first unread message
syzbot
Nov 30, 2022, 2:43:48 AM11/30/22
to syzkaller...@googlegroups.com
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=13f44cad880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=c236c9b8ce6562e4b2eb
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118e585b880000
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/d7f21b29ad21/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c236c9...@syzkaller.appspotmail.com
hfsplus: xattr searching failed
hfsplus: inconsistency in B*Tree (4097,1,255,1,0)
hfsplus: xattr searching failed
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 1 PID: 18294 at fs/hfsplus/bnode.c:584 hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 18294 Comm: syz-executor.2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
Code: b3 05 fa e8 8b 3f 6c f9 4c 89 ef e8 13 0a 23 00 89 ee 48 c7 c7 20 85 7d 88 e8 e0 70 fd ff 48 c7 c7 80 85 7d 88 e8 d4 70 fd ff <0f> 0b e9 47 c6 05 fa e8 5d 3f 6c f9 89 ee 48 c7 c7 c0 82 7d 88 e8
RSP: 0018:ffff88808546e980 EFLAGS: 00010286
RAX: 0000000000000024 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1010a8dd22
RBP: 0000000000000000 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880ac74b800
R13: ffff8880b48bca90 R14: ffff8880b48bc9c0 R15: 0000000000000000
hfsplus_bmap_alloc+0x70b/0x800 fs/hfsplus/btree.c:414
hfs_btree_inc_height.isra.0+0xe6/0x9e0 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x9e1/0xc20 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x489/0x5a0 fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent fs/hfsplus/extents.c:186 [inline]
hfsplus_ext_read_extent+0x910/0xab0 fs/hfsplus/extents.c:218
hfsplus_file_extend+0x672/0xf40 fs/hfsplus/extents.c:461
hfsplus_get_block+0x196/0x960 fs/hfsplus/extents.c:245
__block_write_begin_int+0x46c/0x17b0 fs/buffer.c:1978
__block_write_begin fs/buffer.c:2028 [inline]
block_write_begin+0x58/0x2e0 fs/buffer.c:2087
cont_write_begin+0x55a/0x820 fs/buffer.c:2440
hfsplus_write_begin+0x87/0x150 fs/hfsplus/inode.c:52
generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170
__generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295
generic_file_write_iter+0x3f8/0x730 mm/filemap.c:3323
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
__kernel_write+0x109/0x370 fs/read_write.c:506
dump_emit+0x183/0x300 fs/coredump.c:801
elf_core_dump+0x33c0/0x4c10 fs/binfmt_elf.c:2392
do_coredump+0x1d4e/0x2d60 fs/coredump.c:765
get_signal+0xed9/0x1f70 kernel/signal.c:2583
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode+0x277/0x2d0 arch/x86/entry/common.c:198
retint_user+0x8/0x18
RIP: 0033: (null)
Code: Bad RIP value.
RSP: 002b:0000000020000388 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fcbd8f30f80 RCX: 00007fcbd8e110d9
RDX: 0000000000000000 RSI: 0000000020000380 RDI: 0000000000000000
RBP: 00007fcbd8e6cae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc080b081f R14: 00007fcbd8183300 R15: 0000000000022000
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
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=13f44cad880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=c236c9b8ce6562e4b2eb
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118e585b880000
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/d7f21b29ad21/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c236c9...@syzkaller.appspotmail.com
hfsplus: xattr searching failed
hfsplus: inconsistency in B*Tree (4097,1,255,1,0)
hfsplus: xattr searching failed
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 1 PID: 18294 at fs/hfsplus/bnode.c:584 hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 18294 Comm: syz-executor.2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
Code: b3 05 fa e8 8b 3f 6c f9 4c 89 ef e8 13 0a 23 00 89 ee 48 c7 c7 20 85 7d 88 e8 e0 70 fd ff 48 c7 c7 80 85 7d 88 e8 d4 70 fd ff <0f> 0b e9 47 c6 05 fa e8 5d 3f 6c f9 89 ee 48 c7 c7 c0 82 7d 88 e8
RSP: 0018:ffff88808546e980 EFLAGS: 00010286
RAX: 0000000000000024 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1010a8dd22
RBP: 0000000000000000 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880ac74b800
R13: ffff8880b48bca90 R14: ffff8880b48bc9c0 R15: 0000000000000000
hfsplus_bmap_alloc+0x70b/0x800 fs/hfsplus/btree.c:414
hfs_btree_inc_height.isra.0+0xe6/0x9e0 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x9e1/0xc20 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x489/0x5a0 fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent fs/hfsplus/extents.c:186 [inline]
hfsplus_ext_read_extent+0x910/0xab0 fs/hfsplus/extents.c:218
hfsplus_file_extend+0x672/0xf40 fs/hfsplus/extents.c:461
hfsplus_get_block+0x196/0x960 fs/hfsplus/extents.c:245
__block_write_begin_int+0x46c/0x17b0 fs/buffer.c:1978
__block_write_begin fs/buffer.c:2028 [inline]
block_write_begin+0x58/0x2e0 fs/buffer.c:2087
cont_write_begin+0x55a/0x820 fs/buffer.c:2440
hfsplus_write_begin+0x87/0x150 fs/hfsplus/inode.c:52
generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170
__generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295
generic_file_write_iter+0x3f8/0x730 mm/filemap.c:3323
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
__kernel_write+0x109/0x370 fs/read_write.c:506
dump_emit+0x183/0x300 fs/coredump.c:801
elf_core_dump+0x33c0/0x4c10 fs/binfmt_elf.c:2392
do_coredump+0x1d4e/0x2d60 fs/coredump.c:765
get_signal+0xed9/0x1f70 kernel/signal.c:2583
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode+0x277/0x2d0 arch/x86/entry/common.c:198
retint_user+0x8/0x18
RIP: 0033: (null)
Code: Bad RIP value.
RSP: 002b:0000000020000388 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fcbd8f30f80 RCX: 00007fcbd8e110d9
RDX: 0000000000000000 RSI: 0000000020000380 RDI: 0000000000000000
RBP: 00007fcbd8e6cae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc080b081f R14: 00007fcbd8183300 R15: 0000000000022000
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
syzbot
Dec 7, 2022, 8:28:42 AM12/7/22
to syzkaller...@googlegroups.com
syzbot has found a reproducer for 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=156328fb880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17609433880000
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/4313cbaa9fcf/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c236c9...@syzkaller.appspotmail.com
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
R13: ffff8880b2a86cd0 R14: ffff8880b2a86c00 R15: 0000000000000000
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f28829ea7b9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd7e889758 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f28829ea7b9
RDX: 00000000fffffdef RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00007f28829aa050 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000061e R11: 0000000000000246 R12: 00007f28829aa0e0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=c236c9b8ce6562e4b2eb
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e12929880000
dashboard link: https://syzkaller.appspot.com/bug?extid=c236c9b8ce6562e4b2eb
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17609433880000
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
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c236c9...@syzkaller.appspotmail.com
will be removed in v5.15!
======================================================
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8104 at fs/hfsplus/bnode.c:584 hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
------------[ cut here ]------------
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 8104 Comm: syz-executor298 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
Code: b3 05 fa e8 8b 3f 6c f9 4c 89 ef e8 13 0a 23 00 89 ee 48 c7 c7 20 85 7d 88 e8 e0 70 fd ff 48 c7 c7 80 85 7d 88 e8 d4 70 fd ff <0f> 0b e9 47 c6 05 fa e8 5d 3f 6c f9 89 ee 48 c7 c7 c0 82 7d 88 e8
RSP: 0018:ffff8880b2bdf208 EFLAGS: 00010286
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:hfsplus_bnode_create.cold+0x27/0x4e fs/hfsplus/bnode.c:584
Code: b3 05 fa e8 8b 3f 6c f9 4c 89 ef e8 13 0a 23 00 89 ee 48 c7 c7 20 85 7d 88 e8 e0 70 fd ff 48 c7 c7 80 85 7d 88 e8 d4 70 fd ff <0f> 0b e9 47 c6 05 fa e8 5d 3f 6c f9 89 ee 48 c7 c7 c0 82 7d 88 e8
RAX: 0000000000000024 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed101657be33
RBP: 0000000000000000 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880aa18b400
R13: ffff8880b2a86cd0 R14: ffff8880b2a86c00 R15: 0000000000000000
hfsplus_bmap_alloc+0x70b/0x800 fs/hfsplus/btree.c:414
hfs_btree_inc_height.isra.0+0xe6/0x9e0 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x9e1/0xc20 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x489/0x5a0 fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent fs/hfsplus/extents.c:186 [inline]
hfsplus_ext_read_extent+0x910/0xab0 fs/hfsplus/extents.c:218
hfsplus_file_extend+0x672/0xf40 fs/hfsplus/extents.c:461
hfsplus_get_block+0x196/0x960 fs/hfsplus/extents.c:245
__block_write_begin_int+0x46c/0x17b0 fs/buffer.c:1978
__block_write_begin fs/buffer.c:2028 [inline]
block_write_begin+0x58/0x2e0 fs/buffer.c:2087
cont_write_begin+0x55a/0x820 fs/buffer.c:2440
hfsplus_write_begin+0x87/0x150 fs/hfsplus/inode.c:52
generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170
__generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295
generic_file_write_iter+0x3f8/0x730 mm/filemap.c:3323
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
vfs_write+0x1f3/0x540 fs/read_write.c:549
hfs_btree_inc_height.isra.0+0xe6/0x9e0 fs/hfsplus/brec.c:475
hfsplus_brec_insert+0x9e1/0xc20 fs/hfsplus/brec.c:75
__hfsplus_ext_write_extent+0x489/0x5a0 fs/hfsplus/extents.c:107
__hfsplus_ext_cache_extent fs/hfsplus/extents.c:186 [inline]
hfsplus_ext_read_extent+0x910/0xab0 fs/hfsplus/extents.c:218
hfsplus_file_extend+0x672/0xf40 fs/hfsplus/extents.c:461
hfsplus_get_block+0x196/0x960 fs/hfsplus/extents.c:245
__block_write_begin_int+0x46c/0x17b0 fs/buffer.c:1978
__block_write_begin fs/buffer.c:2028 [inline]
block_write_begin+0x58/0x2e0 fs/buffer.c:2087
cont_write_begin+0x55a/0x820 fs/buffer.c:2440
hfsplus_write_begin+0x87/0x150 fs/hfsplus/inode.c:52
generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170
__generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295
generic_file_write_iter+0x3f8/0x730 mm/filemap.c:3323
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f28829ea7b9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd7e889758 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f28829ea7b9
RDX: 00000000fffffdef RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00007f28829aa050 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000061e R11: 0000000000000246 R12: 00007f28829aa0e0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Reply all
Reply to author
Forward
0 new messages