[v6.1] WARNING in fscrypt_fname_siphash (2)
3 views
Skip to first unread message
syzbot
Nov 10, 2024, 1:13:26 AM11/10/24
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d7039b844a1c Linux 6.1.116
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=157c635f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a047880f6dd12cce
dashboard link: https://syzkaller.appspot.com/bug?extid=9177d065333561cd6fd0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b531abf1deab/disk-d7039b84.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6780cfcf0543/vmlinux-d7039b84.xz
kernel image: https://storage.googleapis.com/syzbot-assets/398543175ad2/bzImage-d7039b84.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9177d0...@syzkaller.appspotmail.com
EXT4-fs (loop6): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop6): 1 truncate cleaned up
EXT4-fs (loop6): mounted filesystem without journal. Quota mode: none.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5617 at fs/crypto/fname.c:567 fscrypt_fname_siphash+0xb9/0xf0
Modules linked in:
CPU: 1 PID: 5617 Comm: syz.6.321 Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:fscrypt_fname_siphash+0xb9/0xf0 fs/crypto/fname.c:567
Code: 42 0f b6 04 28 84 c0 75 38 41 8b 34 24 49 83 c6 40 4c 89 ff 4c 89 f2 5b 41 5c 41 5d 41 5e 41 5f e9 3c 9a 97 08 e8 f7 e1 80 ff <0f> 0b eb aa 89 d9 80 e1 07 38 c1 7c 8c 48 89 df e8 22 6a d8 ff eb
RSP: 0018:ffffc90003daf410 EFLAGS: 00010287
RAX: ffffffff8209aa39 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90003261000 RSI: 0000000000000405 RDI: 0000000000000406
RBP: ffffc90003daf5d0 R08: ffffffff8209a9de R09: ffffffff8236d989
R10: 0000000000000007 R11: ffff8880304d8000 R12: ffffc90003daf560
R13: dffffc0000000000 R14: ffff888058b36180 R15: ffff888070522ad0
FS: 00007f25ba5816c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000061800000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ext4fs_dirhash+0xdd2/0x14c0 fs/ext4/hash.c:268
ext4fs_dirhash+0x1b8/0x320 fs/ext4/hash.c:322
htree_dirblock_to_tree+0x723/0x10d0 fs/ext4/namei.c:1125
ext4_htree_fill_tree+0x73d/0x13f0 fs/ext4/namei.c:1220
ext4_dx_readdir fs/ext4/dir.c:605 [inline]
ext4_readdir+0x2e87/0x3880 fs/ext4/dir.c:142
iterate_dir+0x224/0x560
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x209/0x4f0 fs/readdir.c:354
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f25b977e719
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:00007f25ba581038 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007f25b9935f80 RCX: 00007f25b977e719
RDX: 0000000000000fed RSI: 0000000020000f80 RDI: 0000000000000004
RBP: 00007f25b97f139e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f25b9935f80 R15: 00007ffe8ea7b828
</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
syzbot found the following issue on:
HEAD commit: d7039b844a1c Linux 6.1.116
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=157c635f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a047880f6dd12cce
dashboard link: https://syzkaller.appspot.com/bug?extid=9177d065333561cd6fd0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b531abf1deab/disk-d7039b84.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6780cfcf0543/vmlinux-d7039b84.xz
kernel image: https://storage.googleapis.com/syzbot-assets/398543175ad2/bzImage-d7039b84.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9177d0...@syzkaller.appspotmail.com
EXT4-fs (loop6): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop6): 1 truncate cleaned up
EXT4-fs (loop6): mounted filesystem without journal. Quota mode: none.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5617 at fs/crypto/fname.c:567 fscrypt_fname_siphash+0xb9/0xf0
Modules linked in:
CPU: 1 PID: 5617 Comm: syz.6.321 Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:fscrypt_fname_siphash+0xb9/0xf0 fs/crypto/fname.c:567
Code: 42 0f b6 04 28 84 c0 75 38 41 8b 34 24 49 83 c6 40 4c 89 ff 4c 89 f2 5b 41 5c 41 5d 41 5e 41 5f e9 3c 9a 97 08 e8 f7 e1 80 ff <0f> 0b eb aa 89 d9 80 e1 07 38 c1 7c 8c 48 89 df e8 22 6a d8 ff eb
RSP: 0018:ffffc90003daf410 EFLAGS: 00010287
RAX: ffffffff8209aa39 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90003261000 RSI: 0000000000000405 RDI: 0000000000000406
RBP: ffffc90003daf5d0 R08: ffffffff8209a9de R09: ffffffff8236d989
R10: 0000000000000007 R11: ffff8880304d8000 R12: ffffc90003daf560
R13: dffffc0000000000 R14: ffff888058b36180 R15: ffff888070522ad0
FS: 00007f25ba5816c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000061800000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ext4fs_dirhash+0xdd2/0x14c0 fs/ext4/hash.c:268
ext4fs_dirhash+0x1b8/0x320 fs/ext4/hash.c:322
htree_dirblock_to_tree+0x723/0x10d0 fs/ext4/namei.c:1125
ext4_htree_fill_tree+0x73d/0x13f0 fs/ext4/namei.c:1220
ext4_dx_readdir fs/ext4/dir.c:605 [inline]
ext4_readdir+0x2e87/0x3880 fs/ext4/dir.c:142
iterate_dir+0x224/0x560
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x209/0x4f0 fs/readdir.c:354
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f25b977e719
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:00007f25ba581038 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007f25b9935f80 RCX: 00007f25b977e719
RDX: 0000000000000fed RSI: 0000000020000f80 RDI: 0000000000000004
RBP: 00007f25b97f139e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f25b9935f80 R15: 00007ffe8ea7b828
</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
syzbot
Nov 10, 2024, 1:28:22 AM11/10/24
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: d7039b844a1c Linux 6.1.116
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1012635f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1412635f980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b531abf1deab/disk-d7039b84.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6780cfcf0543/vmlinux-d7039b84.xz
kernel image: https://storage.googleapis.com/syzbot-assets/398543175ad2/bzImage-d7039b84.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/91ea0eb13a00/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9177d0...@syzkaller.appspotmail.com
EXT4-fs (loop0): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop0): 1 truncate cleaned up
EXT4-fs (loop0): mounted filesystem without journal. Quota mode: none.
fscrypt: AES-256-CTS-CBC using implementation "cts-cbc-aes-aesni"
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4245 at fs/crypto/fname.c:567 fscrypt_fname_siphash+0xb9/0xf0
Modules linked in:
CPU: 0 PID: 4245 Comm: syz-executor193 Not tainted 6.1.116-syzkaller #0
RAX: ffffffff8209aa39 RBX: 0000000000000000 RCX: ffff88803164bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003c5f5d0 R08: ffffffff8209a9de R09: ffffffff8236d989
R10: 0000000000000007 R11: ffff88803164bb80 R12: ffffc90003c5f560
R13: dffffc0000000000 R14: ffff888070bda000 R15: ffff88807465b4d8
FS: 000055556e876480(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffb7e003d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007fffb7e003e0 RCX: 00007f74c94b5139
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007fffb7e003e8 R08: 00007f74c9480e60 R09: 00007f74c9480e60
R10: 00007fffb7e003e8 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffb7e00648 R14: 0000000000000001 R15: 0000000000000001
</TASK>
---
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.
HEAD commit: d7039b844a1c Linux 6.1.116
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=a047880f6dd12cce
dashboard link: https://syzkaller.appspot.com/bug?extid=9177d065333561cd6fd0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10471ea7980000
dashboard link: https://syzkaller.appspot.com/bug?extid=9177d065333561cd6fd0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1412635f980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b531abf1deab/disk-d7039b84.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6780cfcf0543/vmlinux-d7039b84.xz
kernel image: https://storage.googleapis.com/syzbot-assets/398543175ad2/bzImage-d7039b84.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9177d0...@syzkaller.appspotmail.com
EXT4-fs (loop0): 1 truncate cleaned up
EXT4-fs (loop0): mounted filesystem without journal. Quota mode: none.
fscrypt: AES-256-CTS-CBC using implementation "cts-cbc-aes-aesni"
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4245 at fs/crypto/fname.c:567 fscrypt_fname_siphash+0xb9/0xf0
Modules linked in:
CPU: 0 PID: 4245 Comm: syz-executor193 Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:fscrypt_fname_siphash+0xb9/0xf0 fs/crypto/fname.c:567
Code: 42 0f b6 04 28 84 c0 75 38 41 8b 34 24 49 83 c6 40 4c 89 ff 4c 89 f2 5b 41 5c 41 5d 41 5e 41 5f e9 3c 9a 97 08 e8 f7 e1 80 ff <0f> 0b eb aa 89 d9 80 e1 07 38 c1 7c 8c 48 89 df e8 22 6a d8 ff eb
RSP: 0018:ffffc90003c5f410 EFLAGS: 00010293
RIP: 0010:fscrypt_fname_siphash+0xb9/0xf0 fs/crypto/fname.c:567
Code: 42 0f b6 04 28 84 c0 75 38 41 8b 34 24 49 83 c6 40 4c 89 ff 4c 89 f2 5b 41 5c 41 5d 41 5e 41 5f e9 3c 9a 97 08 e8 f7 e1 80 ff <0f> 0b eb aa 89 d9 80 e1 07 38 c1 7c 8c 48 89 df e8 22 6a d8 ff eb
RAX: ffffffff8209aa39 RBX: 0000000000000000 RCX: ffff88803164bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003c5f5d0 R08: ffffffff8209a9de R09: ffffffff8236d989
R10: 0000000000000007 R11: ffff88803164bb80 R12: ffffc90003c5f560
R13: dffffc0000000000 R14: ffff888070bda000 R15: ffff88807465b4d8
FS: 000055556e876480(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000024d0f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ext4fs_dirhash+0xdd2/0x14c0 fs/ext4/hash.c:268
ext4fs_dirhash+0x1b8/0x320 fs/ext4/hash.c:322
htree_dirblock_to_tree+0x723/0x10d0 fs/ext4/namei.c:1125
ext4_htree_fill_tree+0x73d/0x13f0 fs/ext4/namei.c:1220
ext4_dx_readdir fs/ext4/dir.c:605 [inline]
ext4_readdir+0x2e87/0x3880 fs/ext4/dir.c:142
iterate_dir+0x224/0x560
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x209/0x4f0 fs/readdir.c:354
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f74c94b5139
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ext4fs_dirhash+0xdd2/0x14c0 fs/ext4/hash.c:268
ext4fs_dirhash+0x1b8/0x320 fs/ext4/hash.c:322
htree_dirblock_to_tree+0x723/0x10d0 fs/ext4/namei.c:1125
ext4_htree_fill_tree+0x73d/0x13f0 fs/ext4/namei.c:1220
ext4_dx_readdir fs/ext4/dir.c:605 [inline]
ext4_readdir+0x2e87/0x3880 fs/ext4/dir.c:142
iterate_dir+0x224/0x560
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x209/0x4f0 fs/readdir.c:354
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffb7e003d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007fffb7e003e0 RCX: 00007f74c94b5139
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007fffb7e003e8 R08: 00007f74c9480e60 R09: 00007f74c9480e60
R10: 00007fffb7e003e8 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffb7e00648 R14: 0000000000000001 R15: 0000000000000001
</TASK>
---
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
Apr 15, 2025, 6:31:09 PM4/15/25
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:
commit 985b67cd86392310d9e9326de941c22fc9340eec
git tree: upstream
Author: Lizhi Xu <lizh...@windriver.com>
Date: Wed Jun 5 01:23:35 2024 +0000
ext4: filesystems without casefold feature cannot be mounted with siphash
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13de08cc580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150d88c0580000
Please keep in mind that other backports might be required as well.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit 985b67cd86392310d9e9326de941c22fc9340eec
git tree: upstream
Author: Lizhi Xu <lizh...@windriver.com>
Date: Wed Jun 5 01:23:35 2024 +0000
ext4: filesystems without casefold feature cannot be mounted with siphash
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13de08cc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a047880f6dd12cce
dashboard link: https://syzkaller.appspot.com/bug?extid=9177d065333561cd6fd0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17cc94e8580000
dashboard link: https://syzkaller.appspot.com/bug?extid=9177d065333561cd6fd0
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150d88c0580000
Please keep in mind that other backports might be required as well.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages