From: syzbot <syzbot+a4ccdd7ebf452e4d4701@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
vasilisalmpanis@gmail.com
Subject: Re: [syzbot] [io-uring?] [block?] memory leak in io_submit_sqes (6)
Date: Tue, 11 Aug 2026 13:39:02 -0700 [thread overview]
Message-ID: <6a7b8866.c5ad36c8.12f49d.001f.GAE@google.com> (raw)
In-Reply-To: <20260811115125.1831170-1-vasilisalmpanis@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a4ccdd7ebf452e4d4701@syzkaller.appspotmail.com
Tested-by: syzbot+a4ccdd7ebf452e4d4701@syzkaller.appspotmail.com
Tested on:
commit: 06cf6189 Merge tag 'x86-urgent-2026-08-08' of git://gi..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=158ce149580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6843f8fd2336602d
dashboard link: https://syzkaller.appspot.com/bug?extid=a4ccdd7ebf452e4d4701
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=17e19879580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-08-11 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 16:51 [syzbot] [io-uring?] [block?] memory leak in io_submit_sqes (6) syzbot
2026-08-11 8:09 ` Forwarded: io_uring/cmd: don't skip completion for a non-armed multishot uring_cmd syzbot
2026-08-11 11:51 ` Vasileios Almpanis
2026-08-11 20:39 ` syzbot [this message]
[not found] <20260811080956.1795709-1-vasilisalmpanis@gmail.com>
2026-08-11 14:14 ` [syzbot] [io-uring?] [block?] memory leak in io_submit_sqes (6) 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=6a7b8866.c5ad36c8.12f49d.001f.GAE@google.com \
--to=syzbot+a4ccdd7ebf452e4d4701@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vasilisalmpanis@gmail.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.