From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f77.google.com (mail-ot1-f77.google.com [209.85.210.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D9197313534 for ; Mon, 1 Dec 2025 17:07:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764608859; cv=none; b=am3IS6LWCXat1nic7zs//W/nF203lDbBclLj/KBqohdpswR92r/tcwj9TYzh0wwDfGpNZ5Xdmw0JDZoGT/ghYDp7POHSZm4hqEl0HC6C4M5NIR5M2SBt41PuTOgiq6Mir8XA2ORLRa+soNCqgt6cgsu/5h11KxLMwgxOuc6hEcU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764608859; c=relaxed/simple; bh=A4sa/7eFVyMZatLPYjUSB1g99hIr7cfbRrD+a7pT1MM=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=M4QLf6fTIsYwKDOwRVF5JShSkh7hi5D4xv5RzgsufJkH8DcZ01ucnxoXNWZAVbuRltNUnqPvYJkdDgfcCvyZKrgvIaqOINSWBE8cazvwRG/5lLm/C9vY96IqdhXhcF+L51ip7GFHlDZeuZobiPNoOw0Y/ZlB6KUlxC4BqNUmQg0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.210.77 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-ot1-f77.google.com with SMTP id 46e09a7af769-7c6de67472dso6316424a34.1 for ; Mon, 01 Dec 2025 09:07:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764608857; x=1765213657; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=PulCKizpA9Z5muYyan2JEvePN99gM26/n4ONZAjRLaA=; b=eY4YLmQNJJujIpbQbkZRvCjtBx2e3TTCtw2pU0TZuWqCT6YjS4Dwt7jXWYZoX5AonZ T0hO6vjsHvZcmIjEQPums1hVuhVZWnoHsS1jAGSBOPc67DI7nvH7SUFB2Brwwe8Z2UtB gPfPpx+cCoqbffeMZSXLhqTlH6KlY2CRWec+GsLJ9qzHYe28BGEGkD5vdbs3uo9GGvFq Do8w6bMRqCO4ZKUupvlx79wCuRaBNGZSiHeu5G2M4ALjf/tNP+pQU8BXwBdzMUB9V+sm xX5y4NRIBxfsMSqdgmfwKlZEzzxvxlfz2/HGB0UKro4BFeweCw7VZ9UaxG9aD4jrY9VA pRxA== X-Forwarded-Encrypted: i=1; AJvYcCUfywhRqqMg24Vmtg5W8hEMQj5xqxG0H0bwZ7s9EAAdzJZ5TuIFtiFv30LncIqlowd5eMI6peIHlnuDj1A=@vger.kernel.org X-Gm-Message-State: AOJu0Yx2JAwbV/PWxeblIgNEsqHkQ4rugV3bGIEuwpud1bvntBvC32Ne xKbwZ5bsd5lb7GrNJlZXfAIDvQ0umbH+rvGdE91oi8lu/rXBGHcsJ9Vv0c1rPMvMoaQ0BfQm6/k C54CNkdaM7ppP9k+gfd7vrmsbfz7vYy/+xnRpOYwkNOWObfjxlIxWChUm2bo= X-Google-Smtp-Source: AGHT+IFlSfztzX02fpjFPCfYx4KjIqVFAZkttn/wUnppyuWaM5s6QZNw5s9GBN2A1wKDhhPMfjoozI4bXjUgVetl4nVPxZlj6eh+ Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:3994:b0:450:d025:d6b with SMTP id 5614622812f47-4514e6aa590mr12321175b6e.16.1764608856815; Mon, 01 Dec 2025 09:07:36 -0800 (PST) Date: Mon, 01 Dec 2025 09:07:36 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <692dcb58.a70a0220.2ea503.00b5.GAE@google.com> Subject: [syzbot] [io-uring?] memory leak in io_submit_sqes (5) From: syzbot To: axboe@kernel.dk, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 7d0a66e4bb90 Linux 6.18 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=110d0512580000 kernel config: https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44 dashboard link: https://syzkaller.appspot.com/bug?extid=641eec6b7af1f62f2b99 compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150d0512580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/3e289f3ec7e8/disk-7d0a66e4.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/bf695f1b8080/vmlinux-7d0a66e4.xz kernel image: https://storage.googleapis.com/syzbot-assets/eb2f95cf98c6/bzImage-7d0a66e4.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+641eec6b7af1f62f2b99@syzkaller.appspotmail.com 2025/12/01 16:45:07 executed programs: 5 BUG: memory leak unreferenced object 0xffff888112d6b200 (size 248): comm "syz.0.17", pid 6070, jiffies 4294944719 hex dump (first 32 bytes): 40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V............. 3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < .............. backtrace (crc 9dd5d643): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497 __io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058 io_alloc_req io_uring/io_uring.h:543 [inline] io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438 __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff888112e96200 (size 248): comm "syz.0.18", pid 6072, jiffies 4294944721 hex dump (first 32 bytes): 40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V............. 3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < .............. backtrace (crc 79b7669c): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497 __io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058 io_alloc_req io_uring/io_uring.h:543 [inline] io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438 __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff888112e5ed00 (size 248): comm "syz.0.19", pid 6073, jiffies 4294944722 hex dump (first 32 bytes): 40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V............. 3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < .............. backtrace (crc 11e3e38b): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497 __io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058 io_alloc_req io_uring/io_uring.h:543 [inline] io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438 __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff888127618400 (size 248): comm "syz.0.20", pid 6127, jiffies 4294945384 hex dump (first 32 bytes): 40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V............. 3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < .............. backtrace (crc b9653957): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497 __io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058 io_alloc_req io_uring/io_uring.h:543 [inline] io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438 __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff8881262cf200 (size 248): comm "syz.0.21", pid 6128, jiffies 4294945385 hex dump (first 32 bytes): 40 f8 56 0d 81 88 ff ff 00 00 00 00 00 00 00 00 @.V............. 3c 20 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 < .............. backtrace (crc 457654b1): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] kmem_cache_alloc_bulk_noprof+0x220/0x3e0 mm/slub.c:7497 __io_alloc_req_refill+0x54/0x1a0 io_uring/io_uring.c:1058 io_alloc_req io_uring/io_uring.h:543 [inline] io_submit_sqes+0x584/0xe80 io_uring/io_uring.c:2438 __do_sys_io_uring_enter+0x83f/0xcf0 io_uring/io_uring.c:3516 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF --- 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. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup