From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH 1/1] io_uring: delay sqarray static branch disablement
Date: Sun, 15 Feb 2026 14:59:24 -0700 [thread overview]
Message-ID: <ad1b654a-d106-45ac-a1db-60b66bf6a917@kernel.dk> (raw)
In-Reply-To: <386f4b36-0c53-4ad7-9f71-dff53345ec4f@gmail.com>
On 2/15/26 2:56 PM, Pavel Begunkov wrote:
> On 2/15/26 21:48, Jens Axboe wrote:
>> On 2/15/26 2:29 PM, Pavel Begunkov wrote:
>>> io_key_has_sqarray static branch can be easily switched
>>> on/off by the user. Prevent abuse and defer for a bit when it's
>>> disabled.
>>
>> Can we get something in here for the reason for why the change
>> is being made? The commit message really doesn't explain any
>> of this.
>
> It appeared to be pretty self-explanatory, I can expand, but in
> short you can spam with
It really wasn't! It says "prevent abuse" but is not specific on what
kind of abuse this is at all.
> while (1) {
> create_ring_with_sq_array();
> kill_ring();
> }
>
> and each iteration it'll be patching kernel code, and that
> can be very disruptive for the entire system depending on arch
> and how removal is synchronized.
OK, so that's the abuse being referred to. I could surely find
out by just checking static_branch_slow_dec_deferred() and
friends, but a commit message should stand by itself and not
need that kind of discovery.
Can you just send a v2 with an updated commit message, please?
--
Jens Axboe
prev parent reply other threads:[~2026-02-15 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 21:29 [PATCH 1/1] io_uring: delay sqarray static branch disablement Pavel Begunkov
2026-02-15 21:48 ` Jens Axboe
2026-02-15 21:56 ` Pavel Begunkov
2026-02-15 21:59 ` 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=ad1b654a-d106-45ac-a1db-60b66bf6a917@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--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