From: syzbot <syzbot+dd02382b022192737ea3@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] WARNING: ODEBUG bug in hfsplus_fill_super (3)
Date: Sun, 08 Sep 2024 04:34:22 -0700 [thread overview]
Message-ID: <0000000000009a38c906219a056f@google.com> (raw)
In-Reply-To: <00000000000047bf6a061d976fdb@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: d1f2d51b711a Merge tag 'clk-fixes-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=147f1ffb980000
kernel config: https://syzkaller.appspot.com/x/.config?x=58a85aa6925a8b78
dashboard link: https://syzkaller.appspot.com/bug?extid=dd02382b022192737ea3
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=11b6589f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127f1ffb980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8b52ee4d6014/disk-d1f2d51b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3409402d9dfd/vmlinux-d1f2d51b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7da5cc92617b/bzImage-d1f2d51b.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/73e23808204f/mount_3.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/0d235c82b3b0/mount_19.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dd02382b022192737ea3@syzkaller.appspotmail.com
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88807c180238 object type: timer_list hint: delayed_sync_fs+0x0/0xf0
WARNING: CPU: 0 PID: 5700 at lib/debugobjects.c:518 debug_print_object+0x17a/0x1f0 lib/debugobjects.c:515
Modules linked in:
CPU: 0 UID: 0 PID: 5700 Comm: syz-executor651 Not tainted 6.11.0-rc6-syzkaller-00326-gd1f2d51b711a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:debug_print_object+0x17a/0x1f0 lib/debugobjects.c:515
Code: e8 0b 84 40 fd 4c 8b 0b 48 c7 c7 40 98 60 8c 48 8b 74 24 08 48 89 ea 44 89 e1 4d 89 f8 ff 34 24 e8 fb 60 9b fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 ec 59 5e 0b 48 83 c4 10 5b 41 5c 41 5d 41 5e 41
RSP: 0018:ffffc9000324f5b8 EFLAGS: 00010286
RAX: 098b313f44a3ce00 RBX: ffffffff8c0cc1a0 RCX: ffff888027455a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffffff8c6099c0 R08: ffffffff8155b372 R09: fffffbfff1cfa0e0
R10: dffffc0000000000 R11: fffffbfff1cfa0e0 R12: 0000000000000000
R13: ffffffff8c6098d8 R14: dffffc0000000000 R15: ffff88807c180238
FS: 00007f7e074f76c0(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000680 CR3: 0000000024282000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
debug_check_no_obj_freed+0x45b/0x580 lib/debugobjects.c:1020
slab_free_hook mm/slub.c:2223 [inline]
slab_free mm/slub.c:4477 [inline]
kfree+0x10f/0x360 mm/slub.c:4598
hfsplus_fill_super+0xf25/0x1ca0 fs/hfsplus/super.c:618
mount_bdev+0x20c/0x2d0 fs/super.c:1679
legacy_get_tree+0xf0/0x190 fs/fs_context.c:662
vfs_get_tree+0x92/0x2b0 fs/super.c:1800
do_new_mount+0x2be/0xb40 fs/namespace.c:3472
do_mount fs/namespace.c:3812 [inline]
__do_sys_mount fs/namespace.c:4020 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3997
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7e0756d80a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 ee 08 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f7e074f6f98 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020002900 RCX: 00007f7e0756d80a
RDX: 0000000020000100 RSI: 0000000020002900 RDI: 00007f7e074f6ff0
RBP: 0000000020000100 R08: 00007f7e074f7030 R09: 00000000000006ca
R10: 0000000002000010 R11: 0000000000000286 R12: 00007f7e074f6ff0
R13: 00007f7e074f7030 R14: 00000000000006d0 R15: 00000000200022c0
</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.
prev parent reply other threads:[~2024-09-08 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 10:48 [syzbot] [hfs?] WARNING: ODEBUG bug in hfsplus_fill_super (3) syzbot
2024-09-08 11:34 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000009a38c906219a056f@google.com \
--to=syzbot+dd02382b022192737ea3@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.