From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Subject: Re: [PATCH for-next] io_uring/query: check for loops in in_query()
Date: Thu, 18 Sep 2025 10:50:55 +0100 [thread overview]
Message-ID: <28ad25c5-94d3-4e30-a04b-2514e825d806@gmail.com> (raw)
In-Reply-To: <2ff474cc-f388-4ec3-a17d-23bf720b46bb@kernel.dk>
On 9/16/25 19:35, Jens Axboe wrote:
> On 9/16/25 12:33 PM, Jens Axboe wrote:
>> On 9/16/25 9:05 AM, Pavel Begunkov wrote:
>>> I'd rather delay non fatal signals and even more so task work
>>> processing, it can't ever be reliable in general case otherwise
>>> and would always need to be executed in a loop. And the execution
>>> should be brief, likely shorter than non-interruptible sections
>>> of many syscalls. In this sense capping at 1000 can be a better
>>> choice.
>>
>> Let's just cap it at 1000, at least that's a more reasonable number. I
>> don't think there's a perfect way to solve this problem, outside of
>> being able to detect loops, but at least 1000 can be documented as the
>> max limit. Not that anyone would ever get anywhere near that...
>
> Forgot to mention, but I'm assuming you'll send a v2 of the patch?
I assumed you'd want to squash something into your patch, but
I can send it out properly.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-09-18 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 0:13 [PATCH for-next] io_uring/query: check for loops in in_query() Jens Axboe
2025-09-11 9:02 ` Pavel Begunkov
2025-09-11 11:40 ` Pavel Begunkov
2025-09-15 18:41 ` Jens Axboe
2025-09-16 15:05 ` Pavel Begunkov
2025-09-16 18:33 ` Jens Axboe
2025-09-16 18:35 ` Jens Axboe
2025-09-18 9:50 ` Pavel Begunkov [this message]
2025-09-18 10:27 ` Pavel Begunkov
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=28ad25c5-94d3-4e30-a04b-2514e825d806@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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