From: syzbot <syzbot+7085977fe51df63eb2bf@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] memory leak in create_io_worker (2)
Date: Tue, 22 Feb 2022 15:40:24 -0800 [thread overview]
Message-ID: <000000000000871dfa05d8a3df7c@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7993e65fdd0f Merge tag 'mtd/fixes-for-5.17-rc5' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b8d5bc700000
kernel config: https://syzkaller.appspot.com/x/.config?x=6668288739b7ad26
dashboard link: https://syzkaller.appspot.com/bug?extid=7085977fe51df63eb2bf
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=17eae25a700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a51236700000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7085977fe51df63eb2bf@syzkaller.appspotmail.com
executing program
executing program
executing program
executing program
executing program
BUG: memory leak
unreferenced object 0xffff888112ec56c0 (size 192):
comm "syz-executor313", pid 30410, jiffies 4294958360 (age 18.100s)
hex dump (first 32 bytes):
01 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:
[<ffffffff816515c6>] kmalloc_node include/linux/slab.h:599 [inline]
[<ffffffff816515c6>] kzalloc_node include/linux/slab.h:726 [inline]
[<ffffffff816515c6>] create_io_worker+0x46/0x250 fs/io-wq.c:812
[<ffffffff81652ab2>] create_worker_cb+0xd2/0xf0 fs/io-wq.c:331
[<ffffffff81273853>] task_work_run+0x73/0xb0 kernel/task_work.c:164
[<ffffffff8163dadd>] tracehook_notify_signal include/linux/tracehook.h:213 [inline]
[<ffffffff8163dadd>] io_run_task_work fs/io_uring.c:2595 [inline]
[<ffffffff8163dadd>] io_run_task_work fs/io_uring.c:2591 [inline]
[<ffffffff8163dadd>] io_run_task_work_sig+0x6d/0x110 fs/io_uring.c:7684
[<ffffffff8164ec75>] io_cqring_wait_schedule fs/io_uring.c:7701 [inline]
[<ffffffff8164ec75>] io_cqring_wait fs/io_uring.c:7770 [inline]
[<ffffffff8164ec75>] __do_sys_io_uring_enter+0x715/0xf60 fs/io_uring.c:10178
[<ffffffff844b4875>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff844b4875>] 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 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
reply other threads:[~2022-02-22 23:40 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 \
--in-reply-to=000000000000871dfa05d8a3df7c@google.com \
--to=syzbot+7085977fe51df63eb2bf@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.