From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Cc: netdev@vger.kernel.org, Kai Aizen <kai@snailsploit.com>
Subject: Re: [PATCH 1/1] io_uring/zcrx: fix user_ref race between scrub and refill paths
Date: Wed, 18 Feb 2026 10:44:24 -0700 [thread overview]
Message-ID: <177143666453.514340.3486576920762114601.b4-ty@kernel.dk> (raw)
In-Reply-To: <364c2e7d4f53b26bb3133cfc4271183fcd450be2.1771435883.git.asml.silence@gmail.com>
On Wed, 18 Feb 2026 17:36:41 +0000, Pavel Begunkov wrote:
> The io_zcrx_put_niov_uref() function uses a non-atomic
> check-then-decrement pattern (atomic_read followed by separate
> atomic_dec) to manipulate user_refs. This is serialized against other
> callers by rq_lock, but io_zcrx_scrub() modifies the same counter with
> atomic_xchg() WITHOUT holding rq_lock.
>
> On SMP systems, the following race exists:
>
> [...]
Applied, thanks!
[1/1] io_uring/zcrx: fix user_ref race between scrub and refill paths
commit: 003049b1c4fb8aabb93febb7d1e49004f6ad653b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-02-18 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 17:36 [PATCH 1/1] io_uring/zcrx: fix user_ref race between scrub and refill paths Pavel Begunkov
2026-02-18 17:44 ` 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=177143666453.514340.3486576920762114601.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=kai@snailsploit.com \
--cc=netdev@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