From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+641eec6b7af1f62f2b99@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
ssranevjti@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] memory leak in io_submit_sqes (5)
Date: Mon, 1 Dec 2025 14:29:38 -0700 [thread overview]
Message-ID: <1425ef9c-dfc5-4802-89fd-d12aa55f93c0@kernel.dk> (raw)
In-Reply-To: <692e0777.a70a0220.2ea503.00bc.GAE@google.com>
On 12/1/25 2:24 PM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> memory leak in io_submit_sqes
Yep that patch made no sense to me...
Shaurya Rane, was that some kind of AI hallucination, or what led to that?!
--
Jens Axboe
next prev parent reply other threads:[~2025-12-01 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 17:07 [syzbot] [io-uring?] memory leak in io_submit_sqes (5) syzbot
2025-12-01 20:16 ` Jens Axboe
2025-12-01 21:00 ` syzbot
2025-12-01 20:36 ` shaurya
2025-12-01 21:24 ` syzbot
2025-12-01 21:29 ` Jens Axboe [this message]
2025-12-01 21:31 ` Jens Axboe
2025-12-01 21:52 ` 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 \
--in-reply-to=1425ef9c-dfc5-4802-89fd-d12aa55f93c0@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssranevjti@gmail.com \
--cc=syzbot+641eec6b7af1f62f2b99@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox