Hello,
syzbot found the following issue on:
HEAD commit: 9247f4e6573a Linux 6.6.98
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=15e668f0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=cfe840f14e117c98
dashboard link:
https://syzkaller.appspot.com/bug?extid=29b46d845126c2686055
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/3855f6db0ca8/disk-9247f4e6.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/fe3d6afeb3a6/vmlinux-9247f4e6.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/7d8784621ac6/bzImage-9247f4e6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+29b46d...@syzkaller.appspotmail.com
EXT4-fs (loop2): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop2): 1 truncate cleaned up
EXT4-fs (loop2): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 12586 at fs/crypto/fname.c:567 fscrypt_fname_siphash+0xa8/0xe0 fs/crypto/fname.c:567
Modules linked in:
CPU: 0 PID: 12586 Comm: syz.2.2181 Not tainted 6.6.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:fscrypt_fname_siphash+0xa8/0xe0 fs/crypto/fname.c:567
Code: 48 89 d8 48 c1 e8 03 42 0f b6 04 20 84 c0 75 32 8b 33 49 83 c6 40 4c 89 f2 5b 41 5c 41 5e 41 5f e9 dd 26 5a 08 e8 68 df 80 ff <0f> 0b eb b3 44 89 f9 80 e1 07 38 c1 7c 9e 4c 89 ff e8 d2 8d d9 ff
RSP: 0018:ffffc900037d6dd8 EFLAGS: 00010283
RAX: ffffffff8204c708 RBX: ffffc900037d6ee0 RCX: 0000000000080000
RDX: ffffc9000d01b000 RSI: 0000000000011514 RDI: 0000000000011515
RBP: ffffc900037d6f50 R08: ffff88807f3c9e00 R09: 0000000000000007
R10: 0000000000000006 R11: 0000000000000002 R12: dffffc0000000000
R13: ffff88806af31c08 R14: ffff88807f557300 R15: ffff88807f557350
FS: 00007f3f9fb806c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055558c422588 CR3: 0000000030c44000 CR4: 00000000003506f0
Call Trace:
<TASK>
__ext4fs_dirhash+0x33f/0xe20 fs/ext4/hash.c:268
ext4fs_dirhash+0x144/0x2c0 fs/ext4/hash.c:322
htree_dirblock_to_tree+0x6cd/0xe70 fs/ext4/namei.c:1125
ext4_htree_fill_tree+0x5db/0x10f0 fs/ext4/namei.c:1220
ext4_dx_readdir fs/ext4/dir.c:608 [inline]
ext4_readdir+0x2b1d/0x39d0 fs/ext4/dir.c:145
iterate_dir+0x1c2/0x580 fs/readdir.c:106
ovl_dir_read+0xfc/0x560 fs/overlayfs/readdir.c:309
ovl_check_d_type_supported+0x99/0x100 fs/overlayfs/readdir.c:1065
ovl_make_workdir fs/overlayfs/super.c:733 [inline]
ovl_get_workdir+0x487/0x1740 fs/overlayfs/super.c:874
ovl_fill_super+0x1345/0x3560 fs/overlayfs/super.c:1427
vfs_get_super fs/super.c:1346 [inline]
get_tree_nodev+0xb5/0x140 fs/super.c:1365
vfs_get_tree+0x8c/0x280 fs/super.c:1764
do_new_mount+0x24b/0xa40 fs/namespace.c:3366
do_mount fs/namespace.c:3706 [inline]
__do_sys_mount fs/namespace.c:3915 [inline]
__se_sys_mount+0x2da/0x3c0 fs/namespace.c:3892
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:0x7f3f9ed8e929
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:00007f3f9fb80038 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f3f9efb5fa0 RCX: 00007f3f9ed8e929
RDX: 0000200000000b80 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f3f9ee10ca1 R08: 0000200000000200 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f3f9efb5fa0 R15: 00007fff0997db58
</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