From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: [syzbot] memory leak in iovec_from_user
Date: Sat, 16 Apr 2022 18:27:21 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: ce522ba9ef7e Linux 5.18-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14225724f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8f1a3425e05af27
dashboard link: https://syzkaller.appspot.com/bug?extid=96b43810dfe9c3bb95ed
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c45d88f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b428af700000
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 0xffff88810d698300 (size 192):
comm "syz-executor156", pid 3595, jiffies 4294944234 (age 12.580s)
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:
[<ffffffff823357be>] kmalloc_array include/linux/slab.h:621 [inline]
[<ffffffff823357be>] iovec_from_user lib/iov_iter.c:1922 [inline]
[<ffffffff823357be>] iovec_from_user+0x13e/0x280 lib/iov_iter.c:1905
[<ffffffff82335945>] __import_iovec+0x45/0x250 lib/iov_iter.c:1948
[<ffffffff81668c8e>] __io_import_iovec+0xfe/0x800 fs/io_uring.c:3497
[<ffffffff8166d92f>] io_import_iovec fs/io_uring.c:3508 [inline]
[<ffffffff8166d92f>] io_read+0x59f/0x880 fs/io_uring.c:3803
[<ffffffff816727b4>] io_issue_sqe+0x364/0x3270 fs/io_uring.c:7122
[<ffffffff816761c3>] __io_queue_sqe fs/io_uring.c:7489 [inline]
[<ffffffff816761c3>] io_queue_sqe fs/io_uring.c:7531 [inline]
[<ffffffff816761c3>] io_submit_sqe fs/io_uring.c:7736 [inline]
[<ffffffff816761c3>] io_submit_sqes+0x553/0x3030 fs/io_uring.c:7842
[<ffffffff81679390>] __do_sys_io_uring_enter+0x6f0/0x1100 fs/io_uring.c:10780
[<ffffffff8451ca25>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff8451ca25>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84600068>] entry_SYSCALL_64_after_hwframe+0x44/0xae
BUG: memory leak
unreferenced object 0xffff88810d6983c0 (size 192):
comm "syz-executor156", pid 3603, jiffies 4294944759 (age 7.330s)
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:
[<ffffffff823357be>] kmalloc_array include/linux/slab.h:621 [inline]
[<ffffffff823357be>] iovec_from_user lib/iov_iter.c:1922 [inline]
[<ffffffff823357be>] iovec_from_user+0x13e/0x280 lib/iov_iter.c:1905
[<ffffffff82335945>] __import_iovec+0x45/0x250 lib/iov_iter.c:1948
[<ffffffff81668c8e>] __io_import_iovec+0xfe/0x800 fs/io_uring.c:3497
[<ffffffff8166d92f>] io_import_iovec fs/io_uring.c:3508 [inline]
[<ffffffff8166d92f>] io_read+0x59f/0x880 fs/io_uring.c:3803
[<ffffffff816727b4>] io_issue_sqe+0x364/0x3270 fs/io_uring.c:7122
[<ffffffff816761c3>] __io_queue_sqe fs/io_uring.c:7489 [inline]
[<ffffffff816761c3>] io_queue_sqe fs/io_uring.c:7531 [inline]
[<ffffffff816761c3>] io_submit_sqe fs/io_uring.c:7736 [inline]
[<ffffffff816761c3>] io_submit_sqes+0x553/0x3030 fs/io_uring.c:7842
[<ffffffff81679390>] __do_sys_io_uring_enter+0x6f0/0x1100 fs/io_uring.c:10780
[<ffffffff8451ca25>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff8451ca25>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84600068>] 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
next reply other threads:[~2022-04-17 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 1:27 syzbot [this message]
2022-04-17 2:17 ` [syzbot] memory leak in iovec_from_user Jens Axboe
2022-04-17 13:27 ` Jens Axboe
2022-04-17 13:37 ` syzbot
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