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 X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 944BDC433E0 for ; Tue, 22 Dec 2020 10:25:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4C94A2310D for ; Tue, 22 Dec 2020 10:25:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726282AbgLVKZA (ORCPT ); Tue, 22 Dec 2020 05:25:00 -0500 Received: from mail-io1-f69.google.com ([209.85.166.69]:57007 "EHLO mail-io1-f69.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725847AbgLVKY7 (ORCPT ); Tue, 22 Dec 2020 05:24:59 -0500 Received: by mail-io1-f69.google.com with SMTP id e14so7084876iow.23 for ; Tue, 22 Dec 2020 02:24:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=upVlXtx35BODx+iT3R6qP2UHaYjqHVnqudOn+NqPxDI=; b=lwxlg1cX8iRBnjI0vfHaN8gMBe8Yz0XZJe045u4tsC75J/ubyr8klB8ipZnRaoAaU8 NTrhVyArHkvbSDaTFN8AKfCNl8Ub4g4Jqa0E9DNPGbXw22MBvLzaJznTnJ/xJsBScSQd 6xzoIqKb6EZjveBt5LojeiPR2hjM2Ht++SQcI3DOa1ZCRdcncKBs8FJ8ts7ueT9QXPaG YlC4EkIEUsVwjnrXcxol1+JrkhorlUpxniKv9QIWdTjNMh7NDp7fMt3a4r0Nog8H3bOv GHzezgeklY98/QWWfbMtjbBXwLEnzT31kdPwZdZMrh9GD6irnVD3Fb6U/tD7lqmOmoHY ruPg== X-Gm-Message-State: AOAM5334ozlhznbVvmeyUSpvunUfauoqSoxyC3EqlOH7Dd+7867aO52i +yZRkT4+s9x7ldcg/pRh83YXF+HGSpuFcJaDKxuAMBwvppNf X-Google-Smtp-Source: ABdhPJwZRCkNPa8yUn/y5TF98qIVZyj652xFtrTfG9ZMYqEuFszOR4DhfjDQSDeipu+QZ/TSH539AR37tqGqUio8hFjMSdUQKfYm MIME-Version: 1.0 X-Received: by 2002:a02:3541:: with SMTP id y1mr18003702jae.66.1608632658296; Tue, 22 Dec 2020 02:24:18 -0800 (PST) Date: Tue, 22 Dec 2020 02:24:18 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000002c029c05b70afacd@google.com> Subject: memory leak in v2_read_file_info From: syzbot To: jack@suse.com, linux-kernel@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: 8653b778 Merge tag 'clk-for-linus' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=153fc4db500000 kernel config: https://syzkaller.appspot.com/x/.config?x=faf2996955887e91 dashboard link: https://syzkaller.appspot.com/bug?extid=77779c9b52ab78154b08 compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11c44960d00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13bc8c0b500000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+77779c9b52ab78154b08@syzkaller.appspotmail.com BUG: memory leak unreferenced object 0xffff888110974f00 (size 64): comm "syz-executor849", pid 8516, jiffies 4294942501 (age 13.960s) hex dump (first 32 bytes): 00 30 ee 0d 81 88 ff ff 00 00 00 00 00 00 00 00 .0.............. 00 00 00 00 00 00 00 00 0a 00 00 00 48 00 00 00 ............H... backtrace: [<0000000018aa1939>] kmalloc include/linux/slab.h:552 [inline] [<0000000018aa1939>] v2_read_file_info+0x1ae/0x430 fs/quota/quota_v2.c:122 [<000000001061252b>] dquot_load_quota_sb+0x351/0x650 fs/quota/dquot.c:2387 [<000000006c1f70f9>] dquot_load_quota_inode fs/quota/dquot.c:2423 [inline] [<000000006c1f70f9>] dquot_load_quota_inode+0xda/0x160 fs/quota/dquot.c:2415 [<00000000abace495>] ext4_quota_enable fs/ext4/super.c:6362 [inline] [<00000000abace495>] ext4_enable_quotas+0x1b2/0x2f0 fs/ext4/super.c:6388 [<00000000b6d6a975>] ext4_fill_super+0x3bc5/0x5ac0 fs/ext4/super.c:5046 [<0000000003a869bd>] mount_bdev+0x223/0x260 fs/super.c:1366 [<000000002138e18c>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:592 [<0000000096e90d3d>] vfs_get_tree+0x28/0x100 fs/super.c:1496 [<00000000eddeeb8e>] do_new_mount fs/namespace.c:2875 [inline] [<00000000eddeeb8e>] path_mount+0xc5e/0x1170 fs/namespace.c:3205 [<00000000c52e2f18>] do_mount fs/namespace.c:3218 [inline] [<00000000c52e2f18>] __do_sys_mount fs/namespace.c:3426 [inline] [<00000000c52e2f18>] __se_sys_mount fs/namespace.c:3403 [inline] [<00000000c52e2f18>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3403 [<00000000e70a31f4>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 [<000000007f651b8c>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 --- 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