Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
	Jens Axboe <axboe@kernel.dk>,
	stable@vger.kernel.org
Cc: Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH 7.0.y,6.18.y 0/2] Backport io_uring commit to affected
Date: Mon, 11 May 2026 10:25:26 +0100	[thread overview]
Message-ID: <852aa66e-60c8-4270-9908-1e72182a6988@gmail.com> (raw)
In-Reply-To: <b2cd99e4-2369-44bb-a7fd-0035241ad0d7@oracle.com>

On 5/8/26 08:52, Harshit Mogalapalli wrote:
> Hi Jens and Pavel,
> 
> On 08/05/26 07:37, Pavel Begunkov wrote:
>> On 5/7/26 23:46, Jens Axboe wrote:
>>> 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.
>>
>> What's motivation for this? I don't mind to have it (after review),
>> but it's not a fix, and I know people want it in stable to claim a
>> hallucinated CVE, and the CVE part is not going to happen.
>>
> 
> Sure, thanks for sharing this. I was reading this: https://ze3tar.github.io/post-zcrx.html and thought of sending backports to affected-stated stable branches. I looked up at the fix and checked probable broken commit and sent these backports. If the report is bogus, I think we should leave these but if its safe to backport these I think we should ?

Got it, thanks for sending the patches, it's better than potentially
overlooking a problem. I'll take a look at as hardening, but the
article refers to non-existent code, the reproducer doesn't reproduce,
it doesn't even do what it says it does, there are one mistake after
another. I took a closer look a week+ ago, and I believe it's all
hallucinations that has never been actually run / validated.

-- 
Pavel Begunkov


  parent reply	other threads:[~2026-05-11  9:25 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
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 [this message]
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=852aa66e-60c8-4270-9908-1e72182a6988@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=vegard.nossum@oracle.com \
    /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