From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f70.google.com (mail-ot1-f70.google.com [209.85.210.70]) (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 CEDB133F385 for ; Fri, 5 Dec 2025 15:04:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.70 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764947049; cv=none; b=Ixe6atds9TAiQe4FUs9CorTYe519H4rhCnGVe5H1puOtwdVlUPUlNEUbttncGUNX6QPFGcTSiFTbTtfnThwaHe2yahpYbQxRT89lLJKsTHCsQNd6okx5n/6yJXS/gGlq87S8PRsYgukWgv5Qlp9nBG1KK0WP96Ze99hFsl9KdbQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764947049; c=relaxed/simple; bh=+RhpHsCpU5wrzqx8j1oGZ5PtyUCGW4rSY4/DVWcL5jE=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=vFMZc60dEo7v/FnymxGXm2hGz3Bvjs1Affnc9hkNS1IoF54PwcDhNFiY6wtAN+YSa0Jjl5LnTZ166lKzf/VjpVh/ctP4Fkf1tSSCEjcI42ZR3X0SqcdocsK14PTZTEWz/WvW3T4pLPKKjHilt8l4bz50WFKG4kSOC4/dMUsf8A4= 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.210.70 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-ot1-f70.google.com with SMTP id 46e09a7af769-7c6d917f184so2035771a34.0 for ; Fri, 05 Dec 2025 07:04:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764947043; x=1765551843; 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=/nrWdOeXcAwcH+7bzXIJSB3QnBNJGlb13TuggU9TNqA=; b=jn7XhzjhdNTtfybywtUd7rDj7OkP70x5+oJS500gBL9Npdmga/pJKNAdtpvhX2d2DQ XInZvDFRL+Kv7CDQwb7TekZ/W8bEuu8Oz7Z7551noxUXolRHV6D0SZN0GKHovX6N7IeR inBwreMWBQU7PfiG47Gt+BwsgJib8nK7Bl3XR0XiZs5LtIN1Xboi0/nTsvGpeENSxYLH kkFKqqgAcY/QvUDvZBMow8vG4Tdxn3vPHJ/VAdCKbWq1aYoP+xZLFPHhKjuEjJDnf1mf QQbco1sGymxUr4B6Hp6WSwhpHcrBdUIDarbX27bwaxDHb4Kl26EFyBH1JTmrkgRc2275 I85g== X-Forwarded-Encrypted: i=1; AJvYcCUJGd4NWyAltnsAHf1nZxDvcJjiKStooMzw9CzB3cakgj0iVJ+FHu9bO+4UGkiMZPs8p1J9Q5HTgklLiZ0=@vger.kernel.org X-Gm-Message-State: AOJu0YxKp7ZgmE0w8dwVpFOJ7hi98wxjs+f2akFpPFIGfGxcZ4+epDzj /Qfn8yFrm1fpjOsmrX+D71RboOnae6hPu85SWpeAKF1IXCs4VZgxHWvB1OfSig2l5b+UfhL5Bk1 0Mx8Y9Xf4o35T8R6OUMyYWQF24nVJQK9cFTqfvGBU63wfPCib4MSCysNC0Ns= X-Google-Smtp-Source: AGHT+IGFhk5WlmdztQlGSAWI4Vg+2u4yTuR04NDiaXZR2V3ChYCi2EOOR4OKjkCspkhiNo3GWkjbftqpXgAlD9VGNAsLX8Nh/LSR 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:1891:b0:44f:e5c8:2902 with SMTP id 5614622812f47-4536e3af545mr5417529b6e.9.1764947043502; Fri, 05 Dec 2025 07:04:03 -0800 (PST) Date: Fri, 05 Dec 2025 07:04:03 -0800 In-Reply-To: <20251205144843.1757055-1-kartikey406@gmail.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6932f463.a70a0220.38f243.0003.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 0xffff888112296400 (size 512): comm "syz.0.17", pid 6722, jiffies 4294946670 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:701 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 0xffff888109a34400 (size 512): comm "syz.0.18", pid 6729, jiffies 4294946674 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:701 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 0xffff888109a34a00 (size 512): comm "syz.0.19", pid 6732, jiffies 4294946677 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:701 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=16b1c41a580000 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=10e25ab4580000