From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH for-6.1] io_uring: disallow self-propelled ring polling
Date: Fri, 18 Nov 2022 09:29:43 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <3124038c0e7474d427538c2d915335ec28c92d21.1668785722.git.asml.silence@gmail.com>
On Fri, 18 Nov 2022 15:41:41 +0000, Pavel Begunkov wrote:
> When we post a CQE we wake all ring pollers as it normally should be.
> However, if a CQE was generated by a multishot poll request targeting
> its own ring, it'll wake that request up, which will make it to post
> a new CQE, which will wake the request and so on until it exhausts all
> CQ entries.
>
> Don't allow multishot polling io_uring files but downgrade them to
> oneshots, which was always stated as a correct behaviour that the
> userspace should check for.
>
> [...]
Applied, thanks!
[1/1] io_uring: disallow self-propelled ring polling
commit: 7fdbc5f014c3f71bc44673a2d6c5bb2d12d45f25
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-18 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 15:41 [PATCH for-6.1] io_uring: disallow self-propelled ring polling Pavel Begunkov
2022-11-18 16:29 ` Jens Axboe [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=166878898377.7355.14584218754403506688.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/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