From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D0AF0C4167D for ; Sun, 12 Nov 2023 04:18:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229935AbjKLESa (ORCPT ); Sat, 11 Nov 2023 23:18:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229867AbjKLES2 (ORCPT ); Sat, 11 Nov 2023 23:18:28 -0500 Received: from mail-pf1-f205.google.com (mail-pf1-f205.google.com [209.85.210.205]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 79C3330E6 for ; Sat, 11 Nov 2023 20:18:25 -0800 (PST) Received: by mail-pf1-f205.google.com with SMTP id d2e1a72fcca58-6b2dff02dfcso3470765b3a.0 for ; Sat, 11 Nov 2023 20:18:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699762705; x=1700367505; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=qWEoTwBlXjGTTrl0xPgTiw5vgCy7bqROUuWjF1tWseI=; b=ZP33HYYn/l2emdJIWEfHoNZYY+klqTUYPHJzp1bqyffOTWnHolCA3XOh+bBXrve+WO LhknNjGH4RsWQ1BEngxcL1D5neOI18mDwze49BvH7a1+wQjCEl7c1pn1UusyONyT7ciQ vp/JCUcxD37D6N8j8KbvcS1l3RGw9zxLNxSKOkL/EMRZxirH+WZ3koVcK4+Mk324Jr2S RgHI7H/kqQO0+vkxkxNMozS7/8FJMvvqRJbmPgtpq0+ouZJXUAT4oZNeH9dY/M5SkeCq oHuvMGDjWq4Xud3PxOJ/wjTqain1xYMSWBnDyhsjtbjBy0LWLp/X6AAgSfDruir9F+33 RAXg== X-Gm-Message-State: AOJu0Yw8aQbNOscj1msHbB5hJCjveAu/hvqGE+fh6ErVFPHrVfOKfjuF llIPUxY5wGMI70Pay8+V+Zx9znbv0Y0kEy69d4XoXlwdtNuC X-Google-Smtp-Source: AGHT+IHZ5YatetUTXqQsCd+tFcdXeuEetfUkqDqzA7IEbmiUgUyTV1jGMi+vSA4VND+qs4KiCqLnYHoIb85f+QrAzPtMoM9IiM0R MIME-Version: 1.0 X-Received: by 2002:a05:6a00:1884:b0:6c6:b762:ad8a with SMTP id x4-20020a056a00188400b006c6b762ad8amr574179pfh.0.1699762705017; Sat, 11 Nov 2023 20:18:25 -0800 (PST) Date: Sat, 11 Nov 2023 20:18:24 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000003c31650609ecd824@google.com> Subject: [syzbot] [overlayfs?] memory leak in ovl_parse_param From: syzbot To: amir73il@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org, miklos@szeredi.hu, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 13d88ac54ddd Merge tag 'vfs-6.7.fsid' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=121cf047680000 kernel config: https://syzkaller.appspot.com/x/.config?x=ecfdf78a410c834 dashboard link: https://syzkaller.appspot.com/bug?extid=26eedf3631650972f17c compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c7a6eb680000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f8b787680000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/9bb27a01f17c/disk-13d88ac5.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/fb496feed171/vmlinux-13d88ac5.xz kernel image: https://storage.googleapis.com/syzbot-assets/f4da22719ffa/bzImage-13d88ac5.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+26eedf3631650972f17c@syzkaller.appspotmail.com executing program BUG: memory leak unreferenced object 0xffff8881009b40a8 (size 8): comm "syz-executor225", pid 5035, jiffies 4294944336 (age 13.730s) hex dump (first 8 bytes): 2e 00 00 00 00 00 00 00 ........ backtrace: [] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [] slab_post_alloc_hook mm/slab.h:766 [inline] [] slab_alloc_node mm/slub.c:3478 [inline] [] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [] __do_kmalloc_node mm/slab_common.c:1006 [inline] [] __kmalloc_node_track_caller+0x4c/0x150 mm/slab_common.c:1027 [] kstrdup+0x3c/0x70 mm/util.c:62 [] ovl_parse_param_lowerdir fs/overlayfs/params.c:496 [inline] [] ovl_parse_param+0x70a/0xc70 fs/overlayfs/params.c:576 [] vfs_parse_fs_param+0xfb/0x190 fs/fs_context.c:146 [] vfs_parse_fs_string+0x96/0xd0 fs/fs_context.c:188 [] vfs_parse_monolithic_sep+0xdf/0x130 fs/fs_context.c:230 [] do_new_mount fs/namespace.c:3333 [inline] [] path_mount+0xc48/0x10d0 fs/namespace.c:3664 [] do_mount fs/namespace.c:3677 [inline] [] __do_sys_mount fs/namespace.c:3886 [inline] [] __se_sys_mount fs/namespace.c:3863 [inline] [] __x64_sys_mount+0x1a1/0x1f0 fs/namespace.c:3863 [] do_syscall_x64 arch/x86/entry/common.c:51 [inline] [] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82 [] entry_SYSCALL_64_after_hwframe+0x63/0x6b BUG: memory leak unreferenced object 0xffff88814002d070 (size 8): comm "syz-executor225", pid 5036, jiffies 4294944900 (age 8.090s) hex dump (first 8 bytes): 2e 00 00 00 00 00 00 00 ........ backtrace: [] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [] slab_post_alloc_hook mm/slab.h:766 [inline] [] slab_alloc_node mm/slub.c:3478 [inline] [] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [] __do_kmalloc_node mm/slab_common.c:1006 [inline] [] __kmalloc_node_track_caller+0x4c/0x150 mm/slab_common.c:1027 [] kstrdup+0x3c/0x70 mm/util.c:62 [] ovl_parse_param_lowerdir fs/overlayfs/params.c:496 [inline] [] ovl_parse_param+0x70a/0xc70 fs/overlayfs/params.c:576 [] vfs_parse_fs_param+0xfb/0x190 fs/fs_context.c:146 [] vfs_parse_fs_string+0x96/0xd0 fs/fs_context.c:188 [] vfs_parse_monolithic_sep+0xdf/0x130 fs/fs_context.c:230 [] do_new_mount fs/namespace.c:3333 [inline] [] path_mount+0xc48/0x10d0 fs/namespace.c:3664 [] do_mount fs/namespace.c:3677 [inline] [] __do_sys_mount fs/namespace.c:3886 [inline] [] __se_sys_mount fs/namespace.c:3863 [inline] [] __x64_sys_mount+0x1a1/0x1f0 fs/namespace.c:3863 [] do_syscall_x64 arch/x86/entry/common.c:51 [inline] [] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82 [] entry_SYSCALL_64_after_hwframe+0x63/0x6b --- 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 syzkaller@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 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 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