public inbox for [email protected]
 help / color / mirror / Atom feed
From: syzbot <[email protected]>
To: [email protected], [email protected],
	[email protected], [email protected],
	[email protected]
Subject: [syzbot] memory leak in io_submit_sqes (3)
Date: Fri, 28 May 2021 23:33:15 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    97e5bf60 Merge branch 'for-5.13-fixes' of git://git.kernel..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a782d3d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b8c23f7848d1c696
dashboard link: https://syzkaller.appspot.com/bug?extid=189b24ff132397acb8fd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=122ff517d00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12cf7cb7d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

executing program
BUG: memory leak
unreferenced object 0xffff888117747500 (size 232):
  comm "syz-executor793", pid 8437, jiffies 4294941760 (age 14.380s)
  hex dump (first 32 bytes):
    00 a2 11 02 81 88 ff ff 18 4e 6f 16 81 88 ff ff  .........No.....
    38 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00  8 .@............
  backtrace:
    [<ffffffff81613299>] io_alloc_req fs/io_uring.c:1707 [inline]
    [<ffffffff81613299>] io_submit_sqes+0x6c9/0x23b0 fs/io_uring.c:6721
    [<ffffffff81615798>] __do_sys_io_uring_enter+0x818/0xf50 fs/io_uring.c:9319
    [<ffffffff8435309a>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
    [<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae

BUG: memory leak
unreferenced object 0xffff888117747400 (size 232):
  comm "syz-executor793", pid 8437, jiffies 4294941760 (age 14.380s)
  hex dump (first 32 bytes):
    00 a2 11 02 81 88 ff ff 18 4e 6f 16 81 88 ff ff  .........No.....
    38 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00  8 .@............
  backtrace:
    [<ffffffff81613299>] io_alloc_req fs/io_uring.c:1707 [inline]
    [<ffffffff81613299>] io_submit_sqes+0x6c9/0x23b0 fs/io_uring.c:6721
    [<ffffffff81615798>] __do_sys_io_uring_enter+0x818/0xf50 fs/io_uring.c:9319
    [<ffffffff8435309a>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
    [<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae

BUG: memory leak
unreferenced object 0xffff888117747300 (size 232):
  comm "syz-executor793", pid 8437, jiffies 4294941760 (age 14.380s)
  hex dump (first 32 bytes):
    00 a2 11 02 81 88 ff ff 18 4e 6f 16 81 88 ff ff  .........No.....
    38 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00  8 .@............
  backtrace:
    [<ffffffff81613299>] io_alloc_req fs/io_uring.c:1707 [inline]
    [<ffffffff81613299>] io_submit_sqes+0x6c9/0x23b0 fs/io_uring.c:6721
    [<ffffffff81615798>] __do_sys_io_uring_enter+0x818/0xf50 fs/io_uring.c:9319
    [<ffffffff8435309a>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
    [<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae

BUG: memory leak
unreferenced object 0xffff888117747200 (size 232):
  comm "syz-executor793", pid 8437, jiffies 4294941760 (age 14.380s)
  hex dump (first 32 bytes):
    00 a2 11 02 81 88 ff ff 18 4e 6f 16 81 88 ff ff  .........No.....
    38 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00  8 .@............
  backtrace:
    [<ffffffff81613299>] io_alloc_req fs/io_uring.c:1707 [inline]
    [<ffffffff81613299>] io_submit_sqes+0x6c9/0x23b0 fs/io_uring.c:6721
    [<ffffffff81615798>] __do_sys_io_uring_enter+0x818/0xf50 fs/io_uring.c:9319
    [<ffffffff8435309a>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
    [<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae

BUG: memory leak
unreferenced object 0xffff888117747100 (size 232):
  comm "syz-executor793", pid 8437, jiffies 4294941760 (age 14.380s)
  hex dump (first 32 bytes):
    00 a2 11 02 81 88 ff ff 18 4e 6f 16 81 88 ff ff  .........No.....
    38 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00  8 .@............
  backtrace:
    [<ffffffff81613299>] io_alloc_req fs/io_uring.c:1707 [inline]
    [<ffffffff81613299>] io_submit_sqes+0x6c9/0x23b0 fs/io_uring.c:6721
    [<ffffffff81615798>] __do_sys_io_uring_enter+0x818/0xf50 fs/io_uring.c:9319
    [<ffffffff8435309a>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
    [<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae

BUG: memory leak
unreferenced object 0xffff88811774acc0 (size 64):
  comm "syz-executor793", pid 8437, jiffies 4294941760 (age 14.380s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 4e 6f 16 81 88 ff ff  .........No.....
    38 20 00 40 00 00 00 00 00 00 00 00 00 00 00 00  8 .@............
  backtrace:
    [<ffffffff81607a9a>] kmalloc include/linux/slab.h:556 [inline]
    [<ffffffff81607a9a>] __io_queue_proc+0x10a/0x1b0 fs/io_uring.c:5027
    [<ffffffff824b8aa6>] poll_wait include/linux/poll.h:51 [inline]
    [<ffffffff824b8aa6>] n_tty_poll+0x76/0x3a0 drivers/tty/n_tty.c:2429
    [<ffffffff824b3319>] tty_poll+0x89/0xc0 drivers/tty/tty_io.c:2231
    [<ffffffff81600e79>] vfs_poll include/linux/poll.h:90 [inline]
    [<ffffffff81600e79>] __io_arm_poll_handler+0xb9/0x2b0 fs/io_uring.c:5118
    [<ffffffff81607137>] io_poll_add.constprop.0+0x47/0x180 fs/io_uring.c:5402
    [<ffffffff8160f6cf>] io_issue_sqe+0x19f/0x2880 fs/io_uring.c:6126
    [<ffffffff81611e4a>] __io_queue_sqe+0x9a/0x620 fs/io_uring.c:6414
    [<ffffffff81612a65>] io_queue_sqe+0x275/0x3e0 fs/io_uring.c:6463
    [<ffffffff81614bf8>] io_submit_sqe fs/io_uring.c:6626 [inline]
    [<ffffffff81614bf8>] io_submit_sqes+0x2028/0x23b0 fs/io_uring.c:6734
    [<ffffffff81615798>] __do_sys_io_uring_enter+0x818/0xf50 fs/io_uring.c:9319
    [<ffffffff8435309a>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
    [<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae



---
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 [email protected].

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

                 reply	other threads:[~2021-05-29  6:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox