Hello,
syzbot found the following issue on:
HEAD commit: 3a8ababb8b6a Linux 6.6.101
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17d6e842580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=a2bd95b6de4839b7
dashboard link:
https://syzkaller.appspot.com/bug?extid=7aabff809b2149af6834
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/f06c672f5fa8/disk-3a8ababb.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/9af9b7afcdc5/vmlinux-3a8ababb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/351a55aafa77/bzImage-3a8ababb.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7aabff...@syzkaller.appspotmail.com
hfs: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7386 at fs/hfs/bnode.c:428 hfs_bnode_create+0x3b9/0x440 fs/hfs/bnode.c:427
Modules linked in:
CPU: 0 PID: 7386 Comm: syz.3.304 Not tainted 6.6.101-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:hfs_bnode_create+0x3b9/0x440 fs/hfs/bnode.c:428
Code: c4 c0 8a 89 ee e8 a7 1b 0c 08 e9 73 fd ff ff e8 ed e5 2f ff 4c 89 ef e8 45 10 21 08 48 c7 c7 20 c5 c0 8a 89 ee e8 87 1b 0c 08 <0f> 0b eb b7 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 7f fc ff ff 4c
RSP: 0018:ffffc90003fc6e18 EFLAGS: 00010246
RAX: 000000000000001f RBX: ffff8880262e6000 RCX: d15ba370410a2a00
RDX: ffffc9000d0ca000 RSI: 0000000000029288 RDI: 0000000000029289
RBP: 0000000000000000 R08: ffff8880b8e28c13 R09: 1ffff110171c5182
R10: dffffc0000000000 R11: ffffed10171c5183 R12: 0000000000000000
R13: ffff8880262e60e0 R14: ffff8880316e1d00 R15: dffffc0000000000
FS: 00007f386f3f36c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0931172020 CR3: 000000002e2b4000 CR4: 00000000003506f0
Call Trace:
<TASK>
hfs_bmap_alloc+0x53b/0x5c0 fs/hfs/btree.c:291
hfs_btree_inc_height+0xf7/0xac0 fs/hfs/brec.c:471
hfs_brec_insert+0x742/0xbd0 fs/hfs/brec.c:148
__hfs_ext_write_extent+0x2a1/0x470 fs/hfs/extent.c:124
__hfs_ext_cache_extent+0x6b/0x9b0 fs/hfs/extent.c:174
hfs_ext_read_extent fs/hfs/extent.c:202 [inline]
hfs_extend_file+0x317/0x1220 fs/hfs/extent.c:401
hfs_get_block+0x3d8/0xbd0 fs/hfs/extent.c:353
__block_write_begin_int+0x566/0x1ad0 fs/buffer.c:2124
__block_write_begin fs/buffer.c:2173 [inline]
block_write_begin+0x9a/0x1e0 fs/buffer.c:2234
cont_write_begin+0x5c8/0x7e0 fs/buffer.c:2591
hfs_write_begin+0x8b/0xd0 fs/hfs/inode.c:58
cont_expand_zero fs/buffer.c:2518 [inline]
cont_write_begin+0x2ad/0x7e0 fs/buffer.c:2581
hfs_write_begin+0x8b/0xd0 fs/hfs/inode.c:58
hfs_file_truncate+0x191/0x9b0 fs/hfs/extent.c:494
hfs_inode_setattr+0x4af/0x6e0 fs/hfs/inode.c:659
notify_change+0xb0d/0xe10 fs/attr.c:499
do_truncate+0x19b/0x220 fs/open.c:66
do_sys_ftruncate+0x325/0x3d0 fs/open.c:194
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f386e58ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f386f3f3038 EFLAGS: 00000246 ORIG_RAX: 000000000000004d
RAX: ffffffffffffffda RBX: 00007f386e7b5fa0 RCX: 00007f386e58ebe9
RDX: 0000000000000000 RSI: 000000000000c17a RDI: 0000000000000004
RBP: 00007f386e611e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f386e7b6038 R14: 00007f386e7b5fa0 R15: 00007fff5fc49928
</TASK>
---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup