Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1500665ybn; Wed, 2 Oct 2019 17:35:13 -0700 (PDT) X-Received: by 2002:a05:6402:1858:: with SMTP id v24mr6805042edy.130.1570062883534; Wed, 02 Oct 2019 17:34:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqxaWCLPPyhNzSNh+Jgoq2YecQU6WgNlX4i71Nc0e30cdvl5chW7m+1lgV7t/p3CxRtyeFZV X-Received: by 2002:a05:6402:1858:: with SMTP id v24mr6804967edy.130.1570062882826; Wed, 02 Oct 2019 17:34:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570062882; cv=none; d=google.com; s=arc-20160816; b=jG3FD3F+NKAU6AzNciYuD1QJ5rmSx6I48m4YYp41uirql0CZ0Fu6FO+/HkyKlYxCIa dffZW8y2r7OsTXs3vhX3AsrGRtL2Cp/+u3WYkmJAKve+4Tdf/Oq3DVRQddo9zgqH2Ncz ahGdzqOXRaQ0mLXQsGDjTZsMBBZm+yQGtmxY47nCdxCZKIqbtkrcaTRQwKrkyfM/Vjzd zkgbmc6BkL4EQ7w5vtZgXxcM99WmS5kQKM1YjfveJeweGb3gr5qXBbhtZePL5NrP1cHA VppdvjlXcY1zh2jHdMi56hzbYn+j+SsLxjFsF7ydiOxVE8btDfg7PUNxKxhb+oe24ZhT DeXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:from:subject:message-id:date :mime-version; bh=peIUdpB0uufhb2WaI0hkt8u3mVPMxGwg5KAkuWXKJEM=; b=HAYODyZ1H/Yiegk5LqkudZDxBdJdTCu8rp4UIuo/p3c11QwNjxFRxjtmmasoOnCxoR oHIFFe7t42Ju1H+QZfcR3qJ6iPbtpZaXEqZ+ga+m8EBVh/u4wKwMLpUosW5rh0sVtBsU jlJzIu7K+aKe4BSzN6CI9RrgrMVaqrA5QNMRR+3ml2Bgfy7eeAUHBe57WQGVDa8BrRzQ qcXfpa3SsYWHQkBJnsrV2m14DNbLEzKSSXaIYimIgKjOZ5yX8yHJQkg0l9ruaKRG+UEf 24NVJezGeiSiUbcD7/KnQK+4/kjVSFCWGZEyVaz13+VdrxEy49T9hqF5lzYy19PgU543 0ohQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id np3si384204ejb.384.2019.10.02.17.34.18; Wed, 02 Oct 2019 17:34:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729466AbfJCATJ (ORCPT + 99 others); Wed, 2 Oct 2019 20:19:09 -0400 Received: from mail-io1-f70.google.com ([209.85.166.70]:32892 "EHLO mail-io1-f70.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729403AbfJCATI (ORCPT ); Wed, 2 Oct 2019 20:19:08 -0400 Received: by mail-io1-f70.google.com with SMTP id g15so2232947ioc.0 for ; Wed, 02 Oct 2019 17:19:08 -0700 (PDT) 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=peIUdpB0uufhb2WaI0hkt8u3mVPMxGwg5KAkuWXKJEM=; b=tlF1mTql75tAOcAP/kd+dLBLkS5A5QgkwHhNfCXCni2ITRjdKt/cRcz+j/+ZLXczkY 8msRT80OPoZS/8gpY7xZwzTrqsnHm5qRaE6BhczxkHTovmoe3Ryo/eOnx4csW9vsP7/m KBFFaVZJGtjaXuy/QjnhsOTZlk6fmavV9f+d8xAK46RiHnqJ/si5CzUTyqfSlOE51ZcE ol5kYYFyNDPyUHvcFOBuTbVLERQzIysEfU8dnVlqYvoOfhDf5XZ3lkgHoi9u04n1mb7R Vmtpl5L1XoQY5JxOPfyGBoxiXCFi4pQFgRCLZrvkDWkEaW0s6bnJETbXJ6T7vmIOGoEE qQRw== X-Gm-Message-State: APjAAAXiiQn8kH5GC4sRMhddQgmswBzy3uXsCERHnO03rF4sw+x11uRz T7xZo4+UD8mp6UGn24z1/tOd7/zwzRdOYB1qIfGPLMI20rkC MIME-Version: 1.0 X-Received: by 2002:a02:7405:: with SMTP id o5mr6859365jac.44.1570061948007; Wed, 02 Oct 2019 17:19:08 -0700 (PDT) Date: Wed, 02 Oct 2019 17:19:08 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000afc1b40593f68888@google.com> Subject: memory leak in gfs2_init_fs_context From: syzbot To: agruenba@redhat.com, cluster-devel@redhat.com, linux-kernel@vger.kernel.org, rpeterso@redhat.com, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following crash on: HEAD commit: f1f2f614 Merge branch 'next-integrity' of git://git.kernel.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15569c05600000 kernel config: https://syzkaller.appspot.com/x/.config?x=4e93436f92b0cfde dashboard link: https://syzkaller.appspot.com/bug?extid=c2fdfd2b783754878fb6 compiler: gcc (GCC) 9.0.0 20181231 (experimental) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10327c05600000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105c9fd5600000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+c2fdfd2b783754878fb6@syzkaller.appspotmail.com udit: type=1400 audit(1569701659.045:64): avc: denied { map } for pid=6842 comm="syz-executor375" path="/root/syz-executor375626622" dev="sda1" ino=16502 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1 executing program executing program BUG: memory leak unreferenced object 0xffff88810fd9a500 (size 256): comm "syz-executor375", pid 6845, jiffies 4294941255 (age 13.550s) 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: [<00000000462ab467>] kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline] [<00000000462ab467>] slab_post_alloc_hook mm/slab.h:586 [inline] [<00000000462ab467>] slab_alloc mm/slab.c:3319 [inline] [<00000000462ab467>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548 [<00000000b1a62211>] kmalloc include/linux/slab.h:552 [inline] [<00000000b1a62211>] kzalloc include/linux/slab.h:686 [inline] [<00000000b1a62211>] gfs2_init_fs_context+0x25/0x90 fs/gfs2/ops_fstype.c:1543 [<00000000db94ecb4>] gfs2_meta_init_fs_context+0x17/0x40 fs/gfs2/ops_fstype.c:1608 [<0000000077df5577>] alloc_fs_context+0x174/0x200 fs/fs_context.c:293 [<000000008d5e3681>] fs_context_for_mount+0x25/0x30 fs/fs_context.c:307 [<0000000030bafbdb>] __do_sys_fsopen fs/fsopen.c:137 [inline] [<0000000030bafbdb>] __se_sys_fsopen fs/fsopen.c:115 [inline] [<0000000030bafbdb>] __x64_sys_fsopen+0xa9/0x1a0 fs/fsopen.c:115 [<00000000974fed69>] do_syscall_64+0x73/0x1f0 arch/x86/entry/common.c:290 [<00000000299e0e1b>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 BUG: memory leak unreferenced object 0xffff88810fd9a200 (size 256): comm "syz-executor375", pid 6846, jiffies 4294941838 (age 7.720s) 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: [<00000000462ab467>] kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline] [<00000000462ab467>] slab_post_alloc_hook mm/slab.h:586 [inline] [<00000000462ab467>] slab_alloc mm/slab.c:3319 [inline] [<00000000462ab467>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548 [<00000000b1a62211>] kmalloc include/linux/slab.h:552 [inline] [<00000000b1a62211>] kzalloc include/linux/slab.h:686 [inline] [<00000000b1a62211>] gfs2_init_fs_context+0x25/0x90 fs/gfs2/ops_fstype.c:1543 [<00000000db94ecb4>] gfs2_meta_init_fs_context+0x17/0x40 fs/gfs2/ops_fstype.c:1608 [<0000000077df5577>] alloc_fs_context+0x174/0x200 fs/fs_context.c:293 [<000000008d5e3681>] fs_context_for_mount+0x25/0x30 fs/fs_context.c:307 [<0000000030bafbdb>] __do_sys_fsopen fs/fsopen.c:137 [inline] [<0000000030bafbdb>] __se_sys_fsopen fs/fsopen.c:115 [inline] [<0000000030bafbdb>] __x64_sys_fsopen+0xa9/0x1a0 fs/fsopen.c:115 [<00000000974fed69>] do_syscall_64+0x73/0x1f0 arch/x86/entry/common.c:290 [<00000000299e0e1b>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 --- This bug 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 bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches