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=-5.7 required=3.0 tests=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 0117AC282CE for ; Thu, 23 May 2019 01:28:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B0EC20B1F for ; Thu, 23 May 2019 01:28:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729675AbfEWB2G (ORCPT ); Wed, 22 May 2019 21:28:06 -0400 Received: from mail-io1-f71.google.com ([209.85.166.71]:45885 "EHLO mail-io1-f71.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727305AbfEWB2F (ORCPT ); Wed, 22 May 2019 21:28:05 -0400 Received: by mail-io1-f71.google.com with SMTP id z2so3351787iog.12 for ; Wed, 22 May 2019 18:28:05 -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=Fl1AYilgXbXs+F9PHNE28XGBtd52ShtQBXn8a0buXtM=; b=rhi+13qCvYnqBWNSYvwuAKC9jxnKBAWDZkwl7BtFbK+IWAZJdTOxD1xA+Um6Qg0aIw 9Wi2soP7RRwS6Tg+9jjhCBF397e7Y+Z93gHp9OoWzAbcBAYtJrkk8e/4XlxZYf4Gt46Q rd/bW7kWyX1hQLeSH+xnXuEl1/DDamXJWfh6eyY6fqNhQqxOIUU0UYmIA5vvLZZ7rFit ztOBqMnRMFyRjdXOItGUDG+5A7hiEEoC//7mQBg+kjC2KGJBBI89BE67nwyPqmcCtyDA NecAdoNQdJkhXAE257eT5GDWWaZf6eSwzon7TDUmbG31qUV+E5WqQSVob0zL1PWbhGDJ gaEQ== X-Gm-Message-State: APjAAAVBRVEJo7d7dreKL6D1SfX8Xmgwp5v2JaRyfl3Mh4YLfXO0yEya 2/FpX+zgrMwpF6Nmv5D05vVf5kAdM5kvDpy1zhgHlmVrg7wr X-Google-Smtp-Source: APXvYqzX0h3gT6teKiHansNya0jnKEok1GtoBkOvu5aNPuUWBhoqjBYyEEdOXS+1Y+vmss07bHjSRq/fWzWtDf2XHMQ8srObdKET MIME-Version: 1.0 X-Received: by 2002:a05:660c:2c5:: with SMTP id j5mr10636325itd.41.1558574884698; Wed, 22 May 2019 18:28:04 -0700 (PDT) Date: Wed, 22 May 2019 18:28:04 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000005bc340058983fe8e@google.com> Subject: memory leak in new_inode_pseudo From: syzbot To: davem@davemloft.net, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, 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: f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12dccd9ca00000 kernel config: https://syzkaller.appspot.com/x/.config?x=61dd9e15a761691d dashboard link: https://syzkaller.appspot.com/bug?extid=111cb28d9f583693aefa compiler: gcc (GCC) 9.0.0 20181231 (experimental) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1587839ca00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16fdb38ca00000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+111cb28d9f583693aefa@syzkaller.appspotmail.com e list of known hosts. executing program BUG: memory leak unreferenced object 0xffff888121bdfd00 (size 632): comm "syz-executor073", pid 7035, jiffies 4294943279 (age 8.130s) hex dump (first 32 bytes): 01 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................ 80 1e b6 1f 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000088b15f0d>] kmemleak_alloc_recursive include/linux/kmemleak.h:55 [inline] [<0000000088b15f0d>] slab_post_alloc_hook mm/slab.h:439 [inline] [<0000000088b15f0d>] slab_alloc mm/slab.c:3326 [inline] [<0000000088b15f0d>] kmem_cache_alloc+0x134/0x270 mm/slab.c:3488 [<000000001a541de3>] sock_alloc_inode+0x1d/0xe0 net/socket.c:252 [<00000000226aca0e>] alloc_inode+0x2c/0xe0 fs/inode.c:226 [<0000000054963a4b>] new_inode_pseudo+0x18/0x70 fs/inode.c:915 [<00000000a577ddf0>] sock_alloc+0x1c/0x90 net/socket.c:575 [<000000000e50448f>] __sock_create+0x8f/0x250 net/socket.c:1394 [<00000000248d5219>] sock_create_kern+0x3b/0x50 net/socket.c:1499 [<0000000081cd440d>] io_uring_get_fd fs/io_uring.c:2997 [inline] [<0000000081cd440d>] io_uring_create fs/io_uring.c:3080 [inline] [<0000000081cd440d>] io_uring_setup+0x4ea/0x990 fs/io_uring.c:3128 [<00000000b95ec5c9>] __do_sys_io_uring_setup fs/io_uring.c:3141 [inline] [<00000000b95ec5c9>] __se_sys_io_uring_setup fs/io_uring.c:3138 [inline] [<00000000b95ec5c9>] __x64_sys_io_uring_setup+0x1a/0x20 fs/io_uring.c:3138 [<0000000072749d9e>] do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301 [<0000000053106e40>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 BUG: memory leak unreferenced object 0xffff88811fb61e80 (size 64): comm "syz-executor073", pid 7035, jiffies 4294943279 (age 8.130s) hex dump (first 32 bytes): 00 00 00 00 81 88 ff ff 88 1e b6 1f 81 88 ff ff ................ 88 1e b6 1f 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<000000008c8eddf3>] kmemleak_alloc_recursive include/linux/kmemleak.h:55 [inline] [<000000008c8eddf3>] slab_post_alloc_hook mm/slab.h:439 [inline] [<000000008c8eddf3>] slab_alloc mm/slab.c:3326 [inline] [<000000008c8eddf3>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553 [<000000005afcf70e>] kmalloc include/linux/slab.h:547 [inline] [<000000005afcf70e>] sock_alloc_inode+0x44/0xe0 net/socket.c:255 [<00000000226aca0e>] alloc_inode+0x2c/0xe0 fs/inode.c:226 [<0000000054963a4b>] new_inode_pseudo+0x18/0x70 fs/inode.c:915 [<00000000a577ddf0>] sock_alloc+0x1c/0x90 net/socket.c:575 [<000000000e50448f>] __sock_create+0x8f/0x250 net/socket.c:1394 [<00000000248d5219>] sock_create_kern+0x3b/0x50 net/socket.c:1499 [<0000000081cd440d>] io_uring_get_fd fs/io_uring.c:2997 [inline] [<0000000081cd440d>] io_uring_create fs/io_uring.c:3080 [inline] [<0000000081cd440d>] io_uring_setup+0x4ea/0x990 fs/io_uring.c:3128 [<00000000b95ec5c9>] __do_sys_io_uring_setup fs/io_uring.c:3141 [inline] [<00000000b95ec5c9>] __se_sys_io_uring_setup fs/io_uring.c:3138 [inline] [<00000000b95ec5c9>] __x64_sys_io_uring_setup+0x1a/0x20 fs/io_uring.c:3138 [<0000000072749d9e>] do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301 [<0000000053106e40>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 BUG: memory leak unreferenced object 0xffff88811dd21c08 (size 56): comm "syz-executor073", pid 7035, jiffies 4294943279 (age 8.130s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30 fd bd 21 81 88 ff ff 20 1c d2 1d 81 88 ff ff 0..!.... ....... backtrace: [<0000000088b15f0d>] kmemleak_alloc_recursive include/linux/kmemleak.h:55 [inline] [<0000000088b15f0d>] slab_post_alloc_hook mm/slab.h:439 [inline] [<0000000088b15f0d>] slab_alloc mm/slab.c:3326 [inline] [<0000000088b15f0d>] kmem_cache_alloc+0x134/0x270 mm/slab.c:3488 [<00000000dec41212>] kmem_cache_zalloc include/linux/slab.h:732 [inline] [<00000000dec41212>] lsm_inode_alloc security/security.c:523 [inline] [<00000000dec41212>] security_inode_alloc+0x33/0xb0 security/security.c:876 [<0000000093ac97c3>] inode_init_always+0x108/0x200 fs/inode.c:168 [<000000006cedb4e8>] alloc_inode+0x49/0xe0 fs/inode.c:233 [<0000000054963a4b>] new_inode_pseudo+0x18/0x70 fs/inode.c:915 [<00000000a577ddf0>] sock_alloc+0x1c/0x90 net/socket.c:575 [<000000000e50448f>] __sock_create+0x8f/0x250 net/socket.c:1394 [<00000000248d5219>] sock_create_kern+0x3b/0x50 net/socket.c:1499 [<0000000081cd440d>] io_uring_get_fd fs/io_uring.c:2997 [inline] [<0000000081cd440d>] io_uring_create fs/io_uring.c:3080 [inline] [<0000000081cd440d>] io_uring_setup+0x4ea/0x990 fs/io_uring.c:3128 [<00000000b95ec5c9>] __do_sys_io_uring_setup fs/io_uring.c:3141 [inline] [<00000000b95ec5c9>] __se_sys_io_uring_setup fs/io_uring.c:3138 [inline] [<00000000b95ec5c9>] __x64_sys_io_uring_setup+0x1a/0x20 fs/io_uring.c:3138 [<0000000072749d9e>] do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301 [<0000000053106e40>] 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