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,URIBL_BLOCKED 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 911A1C64E69 for ; Fri, 20 Nov 2020 15:15:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 68C2F2222F for ; Fri, 20 Nov 2020 15:15:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729352AbgKTPPc (ORCPT ); Fri, 20 Nov 2020 10:15:32 -0500 Received: from mail-io1-f72.google.com ([209.85.166.72]:55962 "EHLO mail-io1-f72.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729314AbgKTPPX (ORCPT ); Fri, 20 Nov 2020 10:15:23 -0500 Received: by mail-io1-f72.google.com with SMTP id j10so7634847iog.22 for ; Fri, 20 Nov 2020 07:15:21 -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=OF6CiG/SEA3+wIoWj8RIQVN5WsLF1TtgPhPsr1W6Mv8=; b=PS9HUtgYJTqM8A9xF8bY+0y6yRX2dZLmyZTsMWfZkd6e3fQ7fUlucUNQvnyZjkOBo5 bKW34aAqgtaJ4wYJYn5i555zS0dJ10TEs7i+8VF+3Ajq0pRJGAjU5okmTnlOchOAvVGk VOLrjdEKpVep0l6Q3e6eVkzIXQ6hHzblLQ17k79S/gipEoxbecMPWG3OdcHZUPpkWhFy axSCe7WjmOCOEj42W+umC7OTVXRSjiYyYsM/2eT15HbhjqvjjRc4ZLyzUEwD+9LuJO7S SSodrPbsBg7uJ9Rey7MM9/DlxUTgcI84ky9ZwasuFUW6FiEhN43ShxYDu06HnFJZ2Jn3 tdWA== X-Gm-Message-State: AOAM530cJ5CjGoaP0sW6q4dJVih+8sP4lNEj4rvHC12JBb3apc93JNdG Lf5CcMO0Tl99cQppJp3lPmzbW/BLvVT1NnOJxt2Ss0bU6WyF X-Google-Smtp-Source: ABdhPJx12JrSVAVPAQQFWy+FWCXh+eEQKGbT2F9NBEefXtNUuGYl3APQZzstxDao66GEVac1ufo7IX3SsgN80cI57AGvL2aHdgTC MIME-Version: 1.0 X-Received: by 2002:a92:ae0e:: with SMTP id s14mr23832161ilh.94.1605885320838; Fri, 20 Nov 2020 07:15:20 -0800 (PST) Date: Fri, 20 Nov 2020 07:15:20 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000019465505b48b50d1@google.com> Subject: memory leak in new_inode From: syzbot To: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org, shaggy@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: c2e7554e Merge tag 'gfs2-v5.10-rc4-fixes' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1362415a500000 kernel config: https://syzkaller.appspot.com/x/.config?x=dc8ee843c1fc6693 dashboard link: https://syzkaller.appspot.com/bug?extid=aa12d6106ea4ca1b6aae compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13a79ea6500000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b62d72500000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+aa12d6106ea4ca1b6aae@syzkaller.appspotmail.com executing program executing program BUG: memory leak unreferenced object 0xffff88810ecc2a80 (size 1280): comm "syz-executor002", pid 8495, jiffies 4294947195 (age 8.020s) 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: [<00000000c920fbb4>] jfs_alloc_inode+0x18/0x60 fs/jfs/super.c:105 [<00000000c664943b>] alloc_inode+0x27/0x100 fs/inode.c:234 [<0000000072a6900b>] new_inode_pseudo fs/inode.c:930 [inline] [<0000000072a6900b>] new_inode+0x23/0x100 fs/inode.c:959 [<0000000022579323>] diReadSpecial+0x28/0x1e0 fs/jfs/jfs_imap.c:424 [<0000000035d6f1c1>] jfs_mount+0xa7/0x280 fs/jfs/jfs_mount.c:107 [<00000000db4745f5>] jfs_fill_super+0x1ad/0x3a0 fs/jfs/super.c:562 [<00000000deb24c86>] mount_bdev+0x223/0x260 fs/super.c:1419 [<00000000355bbcf1>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:592 [<00000000b4778640>] vfs_get_tree+0x28/0x100 fs/super.c:1549 [<00000000661148dd>] do_new_mount fs/namespace.c:2875 [inline] [<00000000661148dd>] path_mount+0xc5e/0x1170 fs/namespace.c:3205 [<00000000184bf2c6>] do_mount fs/namespace.c:3218 [inline] [<00000000184bf2c6>] __do_sys_mount fs/namespace.c:3426 [inline] [<00000000184bf2c6>] __se_sys_mount fs/namespace.c:3403 [inline] [<00000000184bf2c6>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3403 [<000000004af9fc85>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 [<000000004cba2559>] 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