From mboxrd@z Thu Jan 1 00:00:00 1970 From: syzbot Subject: [syzbot] memory leak in nilfs_sysfs_create_device_group Date: Wed, 05 Oct 2022 01:44:40 -0700 Message-ID: <000000000000694b7b05ea45963e@google.com> Mime-Version: 1.0 Return-path: List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Hello, syzbot found the following issue on: HEAD commit: a5088ee7251e Merge tag 'thermal-6.1-rc1' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=153f2492880000 kernel config: https://syzkaller.appspot.com/x/.config?x=21254cf9c7c084e0 dashboard link: https://syzkaller.appspot.com/bug?extid=2e2f697dbd0f429d5dae compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1556a368880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/c2d2c6d22fae/disk-a5088ee7.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/3c66d2393267/vmlinux-a5088ee7.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/f2050cc3fa6c/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2e2f697dbd0f429d5dae-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org BUG: memory leak unreferenced object 0xffff888119526520 (size 32): comm "syz-executor.4", pid 4168, jiffies 4294949450 (age 9.260s) hex dump (first 32 bytes): 6c 6f 6f 70 34 00 00 00 00 00 00 00 00 00 00 00 loop4........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kstrdup+0x36/0x70 mm/util.c:61 [] kstrdup_const+0x53/0x80 mm/util.c:84 [] kvasprintf_const+0xc2/0x110 lib/kasprintf.c:48 [] kobject_set_name_vargs+0x3b/0xe0 lib/kobject.c:257 [] kobject_add_varg lib/kobject.c:352 [inline] [] kobject_init_and_add+0x6d/0xc0 lib/kobject.c:441 [] nilfs_sysfs_create_device_group+0x9a/0x3d0 fs/nilfs2/sysfs.c:991 [] init_nilfs+0x51c/0x680 fs/nilfs2/the_nilfs.c:637 [] nilfs_fill_super fs/nilfs2/super.c:1047 [inline] [] nilfs_mount+0x51b/0x890 fs/nilfs2/super.c:1317 [] legacy_get_tree+0x2b/0x90 fs/fs_context.c:610 [] vfs_get_tree+0x28/0x100 fs/super.c:1530 [] do_new_mount fs/namespace.c:3040 [inline] [] path_mount+0xc37/0x10d0 fs/namespace.c:3370 [] do_mount fs/namespace.c:3383 [inline] [] __do_sys_mount fs/namespace.c:3591 [inline] [] __se_sys_mount fs/namespace.c:3568 [inline] [] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3568 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x63/0xcd --- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches 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 29ACCC433F5 for ; Wed, 5 Oct 2022 08:44:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229530AbiJEIo4 (ORCPT ); Wed, 5 Oct 2022 04:44:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49962 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229957AbiJEIon (ORCPT ); Wed, 5 Oct 2022 04:44:43 -0400 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 749BE5F89 for ; Wed, 5 Oct 2022 01:44:41 -0700 (PDT) Received: by mail-il1-f199.google.com with SMTP id k6-20020a92c246000000b002f80993e780so12837210ilo.13 for ; Wed, 05 Oct 2022 01:44:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=mOh268Wk17ISYAxouxu7muWjraM81l+aStizQFajsq0=; b=iLDB4gUJ/cPCPgn+8C8u8vUfH5TvcEaqiZ/Quf04ttEXWc+sWiL21nevfIScMWI2Vk VLfnnUe0gbwbmcnu0nkO5ZPFWnaRwOoUVXTVMtWkkxQ2B7QaxG5/QdhTjkQdDMxYncYd oRZTD6BP8QCxJ4sSDuPw0VFQUCWMiyVg/v5pIO5AxaDeY6Bm60C91jTE9mnDa72SN+eN UA1W555Fw7RX9/WFYxM5LPiKGrQlP27eMiN5RM84Gay8nSDuyZJHaVHas0d6FW5crSB8 y2C4ijeZmBjMr+p3NKe3vAt9I+BpvSDQhyxPQMghKN849oS3ZuJfz4Qyz0EzUPOnoVEx KV9Q== X-Gm-Message-State: ACrzQf0YqIsihU0y/4kKfwqXlDrLrAJj2UQ7ewiX7xb6IlvmE6WOyosq oZxBEkJU8VP76IqGm9PaUUxKwZcI79G0qo73tvMb5wwNtZeL X-Google-Smtp-Source: AMsMyM5/TfSDT99ZDnmMVQ507JxnFpL0gdqeC06k+60+jf4GW1GIYHmiw2ZUh6hbTge668wki97vz6vy5waiM6mW377SzT/52el/ MIME-Version: 1.0 X-Received: by 2002:a05:6638:3724:b0:362:e8cb:755a with SMTP id k36-20020a056638372400b00362e8cb755amr7577626jav.226.1664959480676; Wed, 05 Oct 2022 01:44:40 -0700 (PDT) Date: Wed, 05 Oct 2022 01:44:40 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000694b7b05ea45963e@google.com> Subject: [syzbot] memory leak in nilfs_sysfs_create_device_group From: syzbot To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org, 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: a5088ee7251e Merge tag 'thermal-6.1-rc1' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=153f2492880000 kernel config: https://syzkaller.appspot.com/x/.config?x=21254cf9c7c084e0 dashboard link: https://syzkaller.appspot.com/bug?extid=2e2f697dbd0f429d5dae compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1556a368880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/c2d2c6d22fae/disk-a5088ee7.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/3c66d2393267/vmlinux-a5088ee7.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/f2050cc3fa6c/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2e2f697dbd0f429d5dae@syzkaller.appspotmail.com BUG: memory leak unreferenced object 0xffff888119526520 (size 32): comm "syz-executor.4", pid 4168, jiffies 4294949450 (age 9.260s) hex dump (first 32 bytes): 6c 6f 6f 70 34 00 00 00 00 00 00 00 00 00 00 00 loop4........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kstrdup+0x36/0x70 mm/util.c:61 [] kstrdup_const+0x53/0x80 mm/util.c:84 [] kvasprintf_const+0xc2/0x110 lib/kasprintf.c:48 [] kobject_set_name_vargs+0x3b/0xe0 lib/kobject.c:257 [] kobject_add_varg lib/kobject.c:352 [inline] [] kobject_init_and_add+0x6d/0xc0 lib/kobject.c:441 [] nilfs_sysfs_create_device_group+0x9a/0x3d0 fs/nilfs2/sysfs.c:991 [] init_nilfs+0x51c/0x680 fs/nilfs2/the_nilfs.c:637 [] nilfs_fill_super fs/nilfs2/super.c:1047 [inline] [] nilfs_mount+0x51b/0x890 fs/nilfs2/super.c:1317 [] legacy_get_tree+0x2b/0x90 fs/fs_context.c:610 [] vfs_get_tree+0x28/0x100 fs/super.c:1530 [] do_new_mount fs/namespace.c:3040 [inline] [] path_mount+0xc37/0x10d0 fs/namespace.c:3370 [] do_mount fs/namespace.c:3383 [inline] [] __do_sys_mount fs/namespace.c:3591 [inline] [] __se_sys_mount fs/namespace.c:3568 [inline] [] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3568 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x63/0xcd --- 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches