From: Jens Axboe <axboe@kernel.dk>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
stable@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH 7.0.y,6.18.y 0/2] Backport io_uring commit to affected
Date: Thu, 7 May 2026 16:46:56 -0600 [thread overview]
Message-ID: <12c809f5-1326-4cd3-9d4d-2bfb011b23e4@kernel.dk> (raw)
In-Reply-To: <5fed66f0-ea72-4f36-bf50-2d7c39c4fdeb@kernel.dk>
On 5/7/26 4:41 PM, Jens Axboe wrote:
> On 5/7/26 6:42 AM, Harshit Mogalapalli wrote:
>> Hi Jens and stable maintainers,
>>
>> The intent of this series is to backport commit: 770594e78c39
>> ("io_uring/zcrx: warn on freelist violations") to 6.18.y and 7.0.y.
>>
>> This above commit likely is fixing commit: 34a3e60821ab ("io_uring/zcrx:
>> implement zerocopy receive pp memory provider") in 6.18.y and 7.0.y.
>>
>> Pulled in a prerequisite to cleanly apply the fix. Only build tested.
>
> I don't think these are actually required, but at the same time it does
> not hurt to add them. I'll leave that to Pavel to decide.
>
> In any case, thanks for doing the backports!
Adding Pavel, I had assumed he was already on the email, as he's the
maintainer for that file.
--
Jens Axboe
next prev parent reply other threads:[~2026-05-07 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 12:42 [PATCH 7.0.y,6.18.y 0/2] Backport io_uring commit to affected Harshit Mogalapalli
2026-05-07 12:42 ` [PATCH 7.0.y,6.18.y 1/2] io_uring/zcrx: use guards for locking Harshit Mogalapalli
2026-05-07 12:42 ` [PATCH 7.0.y,6.18.y 2/2] io_uring/zcrx: warn on freelist violations Harshit Mogalapalli
2026-05-07 22:41 ` [PATCH 7.0.y,6.18.y 0/2] Backport io_uring commit to affected Jens Axboe
2026-05-07 22:46 ` Jens Axboe [this message]
2026-05-08 2:07 ` Pavel Begunkov
2026-05-08 7:52 ` Harshit Mogalapalli
2026-05-08 12:30 ` Jens Axboe
2026-05-11 9:25 ` Pavel Begunkov
2026-05-12 9:37 ` 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=12c809f5-1326-4cd3-9d4d-2bfb011b23e4@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=harshit.m.mogalapalli@oracle.com \
--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