From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot ci <syzbot+ci13e386d4235544e2@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot ci] Re: io_uring: add request poisoning
Date: Sun, 17 Aug 2025 23:08:30 +0100 [thread overview]
Message-ID: <873ab36d-65aa-481a-b056-8f475a56b5e7@gmail.com> (raw)
In-Reply-To: <68a03392.050a0220.e29e5.0041.GAE@google.com>
On 8/16/25 08:30, syzbot ci wrote:
> syzbot ci has tested the following series
>
> [v1] io_uring: add request poisoning
> https://lore.kernel.org/all/b98edbb8ec4495b053dfb11cb3588f17f5253b6e.1755182071.git.asml.silence@gmail.com
> * [PATCH 1/1] io_uring: add request poisoning
>
> and found the following issue:
> general protection fault in __io_queue_proc
It dug up a hack poll_add does to initialise ->async_data. Not a
pre-existent bug, but definitely one of the things the patch is
supposed to uncover. I'll update it.
--
Pavel Begunkov
prev parent reply other threads:[~2025-08-17 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 14:41 [PATCH 1/1] io_uring: add request poisoning Pavel Begunkov
2025-08-16 7:30 ` [syzbot ci] " syzbot ci
2025-08-17 22:08 ` Pavel Begunkov [this message]
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=873ab36d-65aa-481a-b056-8f475a56b5e7@gmail.com \
--to=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=syzbot+ci13e386d4235544e2@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--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