syzbot


memory leak in create_io_worker (2)

Status: auto-obsoleted due to no activity on 2023/06/27 02:40
Subsystems: io-uring fs
[Documentation on labels]
Reported-by: syzbot+7085977fe51df63eb2bf@syzkaller.appspotmail.com
First crash: 759d, last: 489d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] memory leak in create_io_worker (2) 0 (1) 2022/02/22 23:40
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream memory leak in create_io_worker io-uring fs C 5 883d 922d 20/26 fixed on 2021/11/10 00:50
Last patch testing requests (7)
Created Duration User Patch Repo Result
2023/06/27 02:22 18m retest repro upstream OK log
2023/04/18 02:40 17m retest repro upstream OK log
2023/04/18 01:40 17m retest repro upstream OK log
2023/04/18 00:40 22m retest repro upstream report log
2023/04/17 23:40 22m retest repro upstream OK log
2022/11/11 11:30 16m retest repro upstream report log
2022/03/02 03:29 7m phind.uet@gmail.com https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master report log

Sample crash report:
executing program
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88810c9889c0 (size 192):
  comm "syz-executor366", pid 3632, jiffies 4294963262 (age 39.870s)
  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:
    [<ffffffff81699856>] kmalloc_node include/linux/slab.h:618 [inline]
    [<ffffffff81699856>] kzalloc_node include/linux/slab.h:744 [inline]
    [<ffffffff81699856>] create_io_worker+0x46/0x250 fs/io-wq.c:814
    [<ffffffff8169adc2>] create_worker_cb+0xd2/0xf0 fs/io-wq.c:337
    [<ffffffff812787b3>] task_work_run+0x73/0xb0 kernel/task_work.c:177
    [<ffffffff816962b7>] io_run_task_work fs/io_uring.c:3218 [inline]
    [<ffffffff816962b7>] io_run_task_work fs/io_uring.c:3212 [inline]
    [<ffffffff816962b7>] io_run_task_work_sig fs/io_uring.c:9330 [inline]
    [<ffffffff816962b7>] io_cqring_wait_schedule fs/io_uring.c:9348 [inline]
    [<ffffffff816962b7>] io_cqring_wait fs/io_uring.c:9420 [inline]
    [<ffffffff816962b7>] __do_sys_io_uring_enter+0x8c7/0x1300 fs/io_uring.c:12086
    [<ffffffff845b1955>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [<ffffffff845b1955>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [<ffffffff84600087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd


Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/07/30 13:46 upstream e65c6a46df94 fef302b1 .config console log report syz C ci-upstream-gce-leak memory leak in create_io_worker
2022/02/18 23:34 upstream 7993e65fdd0f 3cd800e4 .config console log report syz C ci-upstream-gce-leak memory leak in create_io_worker
2022/11/15 04:09 upstream 094226ad94f4 943f4cb8 .config console log report syz ci-upstream-gce-leak memory leak in create_io_worker
2022/04/17 21:42 upstream a2c29ccd9477 8bcc32a6 .config console log report syz ci-upstream-gce-leak memory leak in create_io_worker
* Struck through repros no longer work on HEAD.