From: Pavel Begunkov <asml.silence@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: io-uring@vger.kernel.org, axboe@kernel.dk,
netdev@vger.kernel.org, stable@vger.kernel.org,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 1/1] io_uring/zcrx: fix post open error handling
Date: Tue, 3 Mar 2026 08:58:21 +0000 [thread overview]
Message-ID: <83689510-1ca6-4429-968c-656031cd1675@gmail.com> (raw)
In-Reply-To: <2026030215-appetite-drastic-5894@gregkh>
On 3/3/26 01:47, Greg KH wrote:
> On Mon, Mar 02, 2026 at 10:15:43PM +0000, Pavel Begunkov wrote:
>> [ upstream commit 5d540e4508950c674d6feef1d95463d039bbf4f5 ]
>>
>> 5d540e4508950 ("io_uring/zcrx: fix post open error handling") fixes some
>> post queue open problems. Instead of picking all dependencies for that
>> patch just move post open error handling out of the way, so once a queue
>> is open we can always report a success.
>>
>> Move copy_to_user earlier before open, and xa_store() should already
>> never fail as the slot is explicitly pre-allocated.
>>
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
>> ---
>> io_uring/zcrx.c | 20 +++++++++-----------
>> 1 file changed, 9 insertions(+), 11 deletions(-)
>
> What stable kernel(s) is this for?
6.18 please
--
Pavel Begunkov
next prev parent reply other threads:[~2026-03-03 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 22:15 [PATCH 1/1] io_uring/zcrx: fix post open error handling Pavel Begunkov
2026-03-02 22:17 ` Pavel Begunkov
2026-03-03 1:47 ` Greg KH
2026-03-03 8:58 ` Pavel Begunkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-14 22:20 Pavel Begunkov
2026-02-15 1:06 ` Jens Axboe
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=83689510-1ca6-4429-968c-656031cd1675@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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