[v6.1] WARNING in hfsplus_free_extents

2 views
Skip to first unread message

syzbot

unread,
Sep 14, 2023, 11:08:51 PM9/14/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 09045dae0d90 Linux 6.1.53
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11a47672680000
kernel config: https://syzkaller.appspot.com/x/.config?x=195b6ef285251409
dashboard link: https://syzkaller.appspot.com/bug?extid=2684e1a866fd9dca0a1a
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=164fdcac680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1227bf1c680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c3b1bb820e74/disk-09045dae.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4c5cfb0563d9/vmlinux-09045dae.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c682edb60d96/bzImage-09045dae.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fc308e7bca96/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2684e1...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 14036 at fs/hfsplus/extents.c:346 hfsplus_free_extents+0x703/0xae0
Modules linked in:
CPU: 1 PID: 14036 Comm: syz-executor146 Not tainted 6.1.53-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:hfsplus_free_extents+0x703/0xae0 fs/hfsplus/extents.c:346
Code: 0f cb 44 89 ef 89 de e8 2b 18 2d ff 41 39 dd 75 20 49 83 c7 28 e8 bd 16 2d ff 41 bc 05 00 00 00 e9 e2 f9 ff ff e8 ad 16 2d ff <0f> 0b e9 83 f9 ff ff 44 89 ef 89 de e8 fc 17 2d ff 41 29 dd 73 0a
RSP: 0018:ffffc90004a9f510 EFLAGS: 00010293
RAX: ffffffff825cfd83 RBX: ffff8880791b5020 RCX: ffff888025b09dc0
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff88807c3d8048
RBP: ffff8880207ca000 R08: dffffc0000000000 R09: ffffed100f87b00a
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000047 R14: ffffc90004a9f630 R15: ffff8880783d6c18
FS: 00007f526d65e6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f526d67fc00 CR3: 000000001f4c1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hfsplus_file_truncate+0x7cc/0xb40 fs/hfsplus/extents.c:591
hfsplus_setattr+0x1b9/0x280 fs/hfsplus/inode.c:269
notify_change+0xdcd/0x1080 fs/attr.c:483
do_truncate+0x21c/0x300 fs/open.c:65
handle_truncate fs/namei.c:3216 [inline]
do_open fs/namei.c:3561 [inline]
path_openat+0x27e2/0x2e60 fs/namei.c:3714
do_filp_open+0x230/0x480 fs/namei.c:3741
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f5275a63c89
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f526d65e218 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f5275aec6e8 RCX: 00007f5275a63c89
RDX: 000000000000275a RSI: 00000000200001c0 RDI: 00000000ffffff9c
RBP: 00007f5275aec6e0 R08: 00007ffeb9b0f167 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5275ab8728
R13: 00007f5275ab806b R14: 00737570635f6576 R15: 0073756c70736668
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages