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=-7.0 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,LONGWORDS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 B2FA7C433E1 for ; Tue, 11 Aug 2020 13:57:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8C620204FD for ; Tue, 11 Aug 2020 13:57:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728727AbgHKN5S (ORCPT ); Tue, 11 Aug 2020 09:57:18 -0400 Received: from mail-io1-f71.google.com ([209.85.166.71]:44167 "EHLO mail-io1-f71.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728516AbgHKN5S (ORCPT ); Tue, 11 Aug 2020 09:57:18 -0400 Received: by mail-io1-f71.google.com with SMTP id m12so9737768iov.11 for ; Tue, 11 Aug 2020 06:57:17 -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=+cHgg9a8eJJddqLe/oCJVSWP9J8KQvuNJEZvME5xXmA=; b=Nt0CTE3ViP0eXpUmpi4QqvDMRBo+8Qf4z+sb+YXCIT+pif6K6IqXHmyMvCdAXxsnOK UO616yrsyjpRPEJSDQ3oGy6vwd+mKqXtno0AzLdM8dfdlZHKL83tt5efatUJ+Bdn3arl Afg+w/v9dH/PoXY3wp9EmNOwwX02ZD4k8LfdY/KkKhlDQMDOG1FV70OLdJXyHCKt0IX7 nRto6Ke5nw1IfACeinFGv/EZerMvP98xhGvhd8FaL/K+OkAI1E3bItDjG7xFppkQNMT7 Cb8+us3TRquQEmzFKfz65335WtvrlH6uMIhElSZDQ4ojEIb4Z1PyAMTkC3C7WjJDS9f1 sVoA== X-Gm-Message-State: AOAM531MBfp+IvOCXi1p4jA5YhgEafZ1ST0WYjto5sEnUN3RqUOrnNYX C6Zo8CqWFDwJqYZhh43JW24kcuGWYD+mqSq3+kta/MuEWSKE X-Google-Smtp-Source: ABdhPJzs9eayEdRluYFEuglfzFGulTDu+xWt1TmqdMl9GvrP3V31DsgZogEIIu9s8vdOXfBs4Z46I6DETIsQ3oOb27AArE8NQjvQ MIME-Version: 1.0 X-Received: by 2002:a02:9307:: with SMTP id d7mr17785704jah.71.1597154237154; Tue, 11 Aug 2020 06:57:17 -0700 (PDT) Date: Tue, 11 Aug 2020 06:57:17 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000f50fb505ac9a72c9@google.com> Subject: memory leak in io_submit_sqes From: syzbot To: axboe@kernel.dk, io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Content-Type: text/plain; charset="UTF-8" Sender: io-uring-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: d6efb3ac Merge tag 'tty-5.9-rc1' of git://git.kernel.org/p.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13cb0762900000 kernel config: https://syzkaller.appspot.com/x/.config?x=42163327839348a9 dashboard link: https://syzkaller.appspot.com/bug?extid=a730016dc0bdce4f6ff5 compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e877dc900000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1608291a900000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a730016dc0bdce4f6ff5@syzkaller.appspotmail.com executing program executing program executing program executing program executing program BUG: memory leak unreferenced object 0xffff888124949100 (size 256): comm "syz-executor808", pid 6480, jiffies 4294949911 (age 33.960s) hex dump (first 32 bytes): 00 78 74 2a 81 88 ff ff 00 00 00 00 00 00 00 00 .xt*............ 90 b0 51 81 ff ff ff ff 00 00 00 00 00 00 00 00 ..Q............. backtrace: [<0000000084e46f34>] io_alloc_req fs/io_uring.c:1503 [inline] [<0000000084e46f34>] io_submit_sqes+0x5dc/0xc00 fs/io_uring.c:6306 [<000000006d4e19eb>] __do_sys_io_uring_enter+0x582/0x830 fs/io_uring.c:8036 [<00000000a4116b07>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 [<0000000067b2aefc>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 BUG: memory leak unreferenced object 0xffff88811751d200 (size 96): comm "syz-executor808", pid 6480, jiffies 4294949911 (age 33.960s) hex dump (first 32 bytes): 00 78 74 2a 81 88 ff ff 00 00 00 00 00 00 00 00 .xt*............ 0e 01 00 00 00 00 75 22 00 00 00 00 00 0f 1f 04 ......u"........ backtrace: [<00000000073ea2ba>] kmalloc include/linux/slab.h:555 [inline] [<00000000073ea2ba>] io_arm_poll_handler fs/io_uring.c:4773 [inline] [<00000000073ea2ba>] __io_queue_sqe+0x445/0x6b0 fs/io_uring.c:5988 [<000000001551bde0>] io_queue_sqe+0x309/0x550 fs/io_uring.c:6060 [<000000002dfb908f>] io_submit_sqe fs/io_uring.c:6130 [inline] [<000000002dfb908f>] io_submit_sqes+0x8b8/0xc00 fs/io_uring.c:6327 [<000000006d4e19eb>] __do_sys_io_uring_enter+0x582/0x830 fs/io_uring.c:8036 [<00000000a4116b07>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 [<0000000067b2aefc>] 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