From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH 1/1] io_uring: fix mixed cqe overflow handling
Date: Tue, 25 Nov 2025 07:04:23 -0700 [thread overview]
Message-ID: <176407946382.1069147.4213690256618739450.b4-ty@kernel.dk> (raw)
In-Reply-To: <3f8137e8c7183817bd7830191764edbd3a59d7f9.1764073533.git.asml.silence@gmail.com>
On Tue, 25 Nov 2025 12:33:06 +0000, Pavel Begunkov wrote:
> I started to see zcrx data corruptions. That turned out to be due
> to CQ tail pointing to a stale entry which happened to be from
> a zcrx request. I.e. the tail is incremented without the CQE
> memory being changed.
>
> The culprit is __io_cqring_overflow_flush() passing "cqe32=true"
> to io_get_cqe_overflow() for non-mixed CQE32 setups, which only
> expects it to be set for mixed 32B CQEs and not for SETUP_CQE32.
>
> [...]
Applied, thanks!
[1/1] io_uring: fix mixed cqe overflow handling
commit: f6dc5a36195d3f5be769f60d6987150192dfb099
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-11-25 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 12:33 [PATCH 1/1] io_uring: fix mixed cqe overflow handling Pavel Begunkov
2025-11-25 14:04 ` 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=176407946382.1069147.4213690256618739450.b4-ty@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