From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f197.google.com (mail-oi1-f197.google.com [209.85.167.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 68E8631B819 for ; Fri, 5 Dec 2025 13:43:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.197 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764942186; cv=none; b=Il9mXEXFEWCrRgeQbNcVBrbcyVvPqr6yz2vJXm5x4sZvleIzc0Lfg1yd4W04QFSa9oSm2Nkh6g1+I3oPRJJSYWehCAyWMcVqxKFpocbUQxna1ohcds6Kg8CeGIiib5gsQ9q5pGK5ur18bh19AN9pLtoZFkvoDxqCVOvzcVXwx94= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764942186; c=relaxed/simple; bh=QRUmznyKrerWtARBzdaOuPfqP5Cb+BUm2ekGT9sXpEg=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=m5+u/8TYxiYH5afQvTufgFR3Nm7dB/zHSIUgG+yxHlBHAsICVqUj1yvKJsz2AjnzHTxYsAdKiEjHrmAR2WBFBJ5n2g5yVlxn7Feoc4cYqtBphzfk9ILC9qnuWK9HLzuEvbeOJDaXJXGi+EUr5w64DCEuOhtSOfpXaAMVvvUqrfs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.197 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f197.google.com with SMTP id 5614622812f47-4538e96a252so721157b6e.1 for ; Fri, 05 Dec 2025 05:43:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764942182; x=1765546982; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6W36F2uaY2M0Odtv9GLU+FTn6o2vLdUZiJwcBcRhAqQ=; b=r+GtobfLJo06DhAxnfswVYSKMFJnJYJKOwLbjVXs4bOcCxvvv05ZbMEIpl/UMULz81 EKmHbzOBJ/UI2W+ZPXVgLvXmE7zqm5DNHBGjGrztN4zr5Vgxt4cLywLZT7kUsbwjtJRf ZOESEI0FIKM9hrHUVBdd5iHlU8tmV1r6FQdutVcN06J9g1OjEh6wLYsMzocbJSe7r2nB yG7GFHmG+wDQgD+VAO4c+TWJbR6Dn16y+gh5gccBoqcBNsiLZRLgm184I6vkADAE46au fJ3VhRHOMnWdPJT8ya6vG+2bHQ9tILAsWdG0XtHlVntlHtZgyPAIQWyZpCLHUojLYdfX wRDA== X-Forwarded-Encrypted: i=1; AJvYcCVn2txhwWlTAgUeXdK9f4xe4PB17H9RyPcdaMYKXA6Ec88tBOeofV/hsuPHP7hToSXNJ6sIiisOCpvXXWc=@vger.kernel.org X-Gm-Message-State: AOJu0Yy7dds75NtO9r5POU8YeNHr8IfV9xXmj6yLS58vGTqEbH2AvEon wYuvYGtWCPY22JZKBktFUX7+Sr6vr3KBbiMZz/imWSz7+cdazuuhFyeBNS7PsR/swFL5fDu2UAn 4WZJPX5oT2CeglqzSRa1s+KKFRe1wUUIqjN7LwrVmLxL1gz8vN/xjV0z7QpY= X-Google-Smtp-Source: AGHT+IFpg+qCYQ15L4GLD2VLs87t1ZTjS8ejaH4wT1Zql0Z3LTDZfb/7fIyBC3V2Z6wfC9tTRaBqMWiuzzeYJmldqrCsvMpN6nqT Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:15a3:b0:44d:b847:ee7e with SMTP id 5614622812f47-45378dd6598mr2255567b6e.1.1764942182139; Fri, 05 Dec 2025 05:43:02 -0800 (PST) Date: Fri, 05 Dec 2025 05:43:02 -0800 In-Reply-To: <20251205124309.1754872-1-kartikey406@gmail.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6932e166.a70a0220.243dc6.0009.GAE@google.com> Subject: Re: [syzbot] [hfs?] memory leak in hfsplus_init_fs_context From: syzbot To: kartikey406@gmail.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: memory leak in hfsplus_init_fs_context BUG: memory leak unreferenced object 0xffff888128616800 (size 512): comm "syz.0.17", pid 6730, jiffies 4294947750 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 8418e967): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4953 [inline] slab_alloc_node mm/slub.c:5258 [inline] __kmalloc_cache_noprof+0x3a6/0x570 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] hfsplus_init_fs_context+0x26/0x90 fs/hfsplus/super.c:700 alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315 do_new_mount fs/namespace.c:3692 [inline] path_mount+0x93f/0x1320 fs/namespace.c:4022 do_mount fs/namespace.c:4035 [inline] __do_sys_mount fs/namespace.c:4224 [inline] __se_sys_mount fs/namespace.c:4201 [inline] __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff888128617600 (size 512): comm "syz.0.18", pid 6734, jiffies 4294947753 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 8418e967): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4953 [inline] slab_alloc_node mm/slub.c:5258 [inline] __kmalloc_cache_noprof+0x3a6/0x570 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] hfsplus_init_fs_context+0x26/0x90 fs/hfsplus/super.c:700 alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315 do_new_mount fs/namespace.c:3692 [inline] path_mount+0x93f/0x1320 fs/namespace.c:4022 do_mount fs/namespace.c:4035 [inline] __do_sys_mount fs/namespace.c:4224 [inline] __se_sys_mount fs/namespace.c:4201 [inline] __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff8881274f3800 (size 512): comm "syz.0.19", pid 6739, jiffies 4294947757 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 8418e967): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4953 [inline] slab_alloc_node mm/slub.c:5258 [inline] __kmalloc_cache_noprof+0x3a6/0x570 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] hfsplus_init_fs_context+0x26/0x90 fs/hfsplus/super.c:700 alloc_fs_context+0x2a0/0x6e0 fs/fs_context.c:315 do_new_mount fs/namespace.c:3692 [inline] path_mount+0x93f/0x1320 fs/namespace.c:4022 do_mount fs/namespace.c:4035 [inline] __do_sys_mount fs/namespace.c:4224 [inline] __se_sys_mount fs/namespace.c:4201 [inline] __x64_sys_mount+0x1a2/0x1e0 fs/namespace.c:4201 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF Tested on: commit: 2061f18a Merge tag 'caps-pr-20251204' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15e6c41a580000 kernel config: https://syzkaller.appspot.com/x/.config?x=4ec6d85125e91f07 dashboard link: https://syzkaller.appspot.com/bug?extid=99f6ed51479b86ac4c41 compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 patch: https://syzkaller.appspot.com/x/patch.diff?x=10b2c41a580000