[v6.6] kernel BUG in __hfsplus_setxattr
1 view
Skip to first unread message
syzbot
Jul 30, 2025, 3:34:32 PM7/30/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15178834580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
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/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7c77d6...@syzkaller.appspotmail.com
loop5: detected capacity change from 0 to 1024
------------[ cut here ]------------
kernel BUG at fs/hfsplus/xattr.c:175!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9966 Comm: syz.5.10995 Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RSP: 0018:ffffc9000cf9f5a0 EFLAGS: 00010283
RAX: ffffffff8255332d RBX: ffff888067cb2000 RCX: 0000000000080000
RDX: ffffc90012495000 RSI: 0000000000004a42 RDI: 0000000000004a43
RBP: ffffc9000cf9fa38 R08: ffff8880305fe78b R09: 1ffff110060bfcf1
R10: dffffc0000000000 R11: ffffed10060bfcf2 R12: ffff8880305fe6f0
R13: 1ffff920019f3ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 00007f281fd906c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2fe1fffc CR3: 000000005f4f7000 CR4: 00000000003506e0
Call Trace:
<TASK>
hfsplus_setxattr+0x11e/0x170 fs/hfsplus/xattr.c:434
hfsplus_security_setxattr+0x40/0x50 fs/hfsplus/xattr_security.c:31
__vfs_setxattr+0x431/0x470 fs/xattr.c:201
__vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235
vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322
do_setxattr fs/xattr.c:630 [inline]
path_setxattr+0x362/0x550 fs/xattr.c:659
__do_sys_setxattr fs/xattr.c:677 [inline]
__se_sys_setxattr fs/xattr.c:673 [inline]
__x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:673
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:0x7f281ef8e9a9
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:00007f281fd90038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f281f1b5fa0 RCX: 00007f281ef8e9a9
RDX: 0000000000000000 RSI: 0000200000000300 RDI: 00002000000002c0
RBP: 00007f281f010d69 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f281f1b5fa0 R15: 00007fffde0ae3e8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RSP: 0018:ffffc9000cf9f5a0 EFLAGS: 00010283
RAX: ffffffff8255332d RBX: ffff888067cb2000 RCX: 0000000000080000
RDX: ffffc90012495000 RSI: 0000000000004a42 RDI: 0000000000004a43
RBP: ffffc9000cf9fa38 R08: ffff8880305fe78b R09: 1ffff110060bfcf1
R10: dffffc0000000000 R11: ffffed10060bfcf2 R12: ffff8880305fe6f0
R13: 1ffff920019f3ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 00007f281fd906c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbbfbb71de0 CR3: 000000005f4f7000 CR4: 00000000003506f0
---
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: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15178834580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
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/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7c77d6...@syzkaller.appspotmail.com
loop5: detected capacity change from 0 to 1024
------------[ cut here ]------------
kernel BUG at fs/hfsplus/xattr.c:175!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9966 Comm: syz.5.10995 Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RSP: 0018:ffffc9000cf9f5a0 EFLAGS: 00010283
RAX: ffffffff8255332d RBX: ffff888067cb2000 RCX: 0000000000080000
RDX: ffffc90012495000 RSI: 0000000000004a42 RDI: 0000000000004a43
RBP: ffffc9000cf9fa38 R08: ffff8880305fe78b R09: 1ffff110060bfcf1
R10: dffffc0000000000 R11: ffffed10060bfcf2 R12: ffff8880305fe6f0
R13: 1ffff920019f3ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 00007f281fd906c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2fe1fffc CR3: 000000005f4f7000 CR4: 00000000003506e0
Call Trace:
<TASK>
hfsplus_setxattr+0x11e/0x170 fs/hfsplus/xattr.c:434
hfsplus_security_setxattr+0x40/0x50 fs/hfsplus/xattr_security.c:31
__vfs_setxattr+0x431/0x470 fs/xattr.c:201
__vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235
vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322
do_setxattr fs/xattr.c:630 [inline]
path_setxattr+0x362/0x550 fs/xattr.c:659
__do_sys_setxattr fs/xattr.c:677 [inline]
__se_sys_setxattr fs/xattr.c:673 [inline]
__x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:673
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:0x7f281ef8e9a9
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:00007f281fd90038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f281f1b5fa0 RCX: 00007f281ef8e9a9
RDX: 0000000000000000 RSI: 0000200000000300 RDI: 00002000000002c0
RBP: 00007f281f010d69 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f281f1b5fa0 R15: 00007fffde0ae3e8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RSP: 0018:ffffc9000cf9f5a0 EFLAGS: 00010283
RAX: ffffffff8255332d RBX: ffff888067cb2000 RCX: 0000000000080000
RDX: ffffc90012495000 RSI: 0000000000004a42 RDI: 0000000000004a43
RBP: ffffc9000cf9fa38 R08: ffff8880305fe78b R09: 1ffff110060bfcf1
R10: dffffc0000000000 R11: ffffed10060bfcf2 R12: ffff8880305fe6f0
R13: 1ffff920019f3ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 00007f281fd906c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbbfbb71de0 CR3: 000000005f4f7000 CR4: 00000000003506f0
---
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
Jul 30, 2025, 4:07:29 PM7/30/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15cf8834580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d02ca2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fd26ad46dafc/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7c77d6...@syzkaller.appspotmail.com
syz.0.16[5940]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
loop0: detected capacity change from 0 to 1024
RAX: ffffffff8255332d RBX: ffff888076ede000 RCX: ffff88807c559e00
RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000000
RBP: ffffc90003317a38 R08: ffff8880311aaacb R09: 1ffff11006235559
R10: dffffc0000000000 R11: ffffed100623555a R12: ffff8880311aaa30
R13: 1ffff92000662ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 000055559313d500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
RAX: ffffffffffffffda RBX: 00007f4198bb5fa0 RCX: 00007f419898e9a9
RAX: ffffffff8255332d RBX: ffff888076ede000 RCX: ffff88807c559e00
RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000000
RBP: ffffc90003317a38 R08: ffff8880311aaacb R09: 1ffff11006235559
R10: dffffc0000000000 R11: ffffed100623555a R12: ffff8880311aaa30
R13: 1ffff92000662ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 000055559313d500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
---
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: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115bccf0580000
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d02ca2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7c77d6...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 1024
------------[ cut here ]------------
kernel BUG at fs/hfsplus/xattr.c:175!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5940 Comm: syz.0.16 Not tainted 6.6.100-syzkaller #0
kernel BUG at fs/hfsplus/xattr.c:175!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RSP: 0018:ffffc900033175a0 EFLAGS: 00010293
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RAX: ffffffff8255332d RBX: ffff888076ede000 RCX: ffff88807c559e00
RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000000
RBP: ffffc90003317a38 R08: ffff8880311aaacb R09: 1ffff11006235559
R10: dffffc0000000000 R11: ffffed100623555a R12: ffff8880311aaa30
R13: 1ffff92000662ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 000055559313d500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2bf5ffff CR3: 0000000075a5e000 CR4: 00000000003506f0
Call Trace:
<TASK>
hfsplus_setxattr+0x11e/0x170 fs/hfsplus/xattr.c:434
hfsplus_security_setxattr+0x40/0x50 fs/hfsplus/xattr_security.c:31
__vfs_setxattr+0x431/0x470 fs/xattr.c:201
__vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235
vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322
do_setxattr fs/xattr.c:630 [inline]
path_setxattr+0x362/0x550 fs/xattr.c:659
__do_sys_setxattr fs/xattr.c:677 [inline]
__se_sys_setxattr fs/xattr.c:673 [inline]
__x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:673
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:0x7f419898e9a9
<TASK>
hfsplus_setxattr+0x11e/0x170 fs/hfsplus/xattr.c:434
hfsplus_security_setxattr+0x40/0x50 fs/hfsplus/xattr_security.c:31
__vfs_setxattr+0x431/0x470 fs/xattr.c:201
__vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235
vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322
do_setxattr fs/xattr.c:630 [inline]
path_setxattr+0x362/0x550 fs/xattr.c:659
__do_sys_setxattr fs/xattr.c:677 [inline]
__se_sys_setxattr fs/xattr.c:673 [inline]
__x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:673
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
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:00007ffd2a78f558 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f4198bb5fa0 RCX: 00007f419898e9a9
RDX: 0000000000000000 RSI: 0000200000000300 RDI: 00002000000002c0
RBP: 00007f4198a10d69 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4198bb5fa0 R14: 00007f4198bb5fa0 R15: 0000000000000005
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RSP: 0018:ffffc900033175a0 EFLAGS: 00010293
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfsplus_create_attributes_file fs/hfsplus/xattr.c:175 [inline]
RIP: 0010:__hfsplus_setxattr+0x1edd/0x1ef0 fs/hfsplus/xattr.c:331
Code: a8 87 ff e9 96 fb ff ff e8 70 62 30 ff 4c 89 e7 48 c7 c6 20 c0 c0 8a e8 81 23 70 ff 0f 0b e8 5a 62 30 ff 0f 0b e8 53 62 30 ff <0f> 0b e8 4c 62 30 ff e9 fa f4 ff ff 0f 1f 80 00 00 00 00 41 56 53
RAX: ffffffff8255332d RBX: ffff888076ede000 RCX: ffff88807c559e00
RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000000
RBP: ffffc90003317a38 R08: ffff8880311aaacb R09: 1ffff11006235559
R10: dffffc0000000000 R11: ffffed100623555a R12: ffff8880311aaa30
R13: 1ffff92000662ecc R14: 0000000000010000 R15: dffffc0000000000
FS: 000055559313d500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2bf5ffff CR3: 0000000075a5e000 CR4: 00000000003506f0
---
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
Aug 21, 2025, 11:23:05 PM8/21/25
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:
commit c7c6363ca186747ebc2df10c8a1a51e66e0e32d9
git tree: upstream
Author: Tetsuo Handa <penguin...@I-love.SAKURA.ne.jp>
Date: Tue Jul 15 05:17:56 2025 +0000
hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10bfffa2580000
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit c7c6363ca186747ebc2df10c8a1a51e66e0e32d9
git tree: upstream
Author: Tetsuo Handa <penguin...@I-love.SAKURA.ne.jp>
Date: Tue Jul 15 05:17:56 2025 +0000
hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10bfffa2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115bccf0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d02ca2580000
Please keep in mind that other backports might be required as well.
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d02ca2580000
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Aug 28, 2025, 5:27:06 PM8/28/25
to syzkaller...@googlegroups.com
The commit that was suspected to fix the issue was backported to the fuzzed
kernel trees.
commit b3359392b75395a31af739a761f48f4041148226
Author: <penguin...@I-love.SAKURA.ne.jp>
#syz fix: hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
The commit was initially detected here:
commit c7c6363ca186747ebc2df10c8a1a51e66e0e32d9
git tree: upstream
Author: Tetsuo Handa <penguin...@I-love.SAKURA.ne.jp>
Date: Tue Jul 15 05:17:56 2025 +0000
hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10bfffa2580000
kernel trees.
commit b3359392b75395a31af739a761f48f4041148226
Author: <penguin...@I-love.SAKURA.ne.jp>
Date: Tue Jul 15 05:17:56 2025 +0000
hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
If you believe this is correct, please reply with
hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
#syz fix: hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
The commit was initially detected here:
commit c7c6363ca186747ebc2df10c8a1a51e66e0e32d9
git tree: upstream
Author: Tetsuo Handa <penguin...@I-love.SAKURA.ne.jp>
Date: Tue Jul 15 05:17:56 2025 +0000
hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10bfffa2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
dashboard link: https://syzkaller.appspot.com/bug?extid=7c77d64bd43394c8b8eb
Reply all
Reply to author
Forward
0 new messages