Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Pumpkin Chang <pumpkin@devco.re>
Subject: Re: [PATCH 6.12.y 6.13.y] io_uring/kbuf: reallocate buf lists on upgrade
Date: Wed, 19 Feb 2025 12:13:52 +0000	[thread overview]
Message-ID: <f2f9e3ba-07fd-4fb0-ad05-893ef41a1a3f@gmail.com> (raw)
In-Reply-To: <2025021941-getaway-polish-00a9@gregkh>

On 2/19/25 05:53, Greg KH wrote:
> On Wed, Feb 19, 2025 at 01:30:04AM +0000, Pavel Begunkov wrote:
>> On 2/19/25 01:28, Pavel Begunkov wrote:
>>> [ upstream commit 8802766324e1f5d414a81ac43365c20142e85603 ]
>>>
>>> IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it
>>> was created for legacy selected buffer and has been emptied. It violates
>>> the requirement that most of the field should stay stable after publish.
>>> Always reallocate it instead.
>>
>> Just a note that it should apply to 6.13 and 6.12, can you
>> pick it for both of them?
> 
> Now done, thanks!

Great, thanks

-- 
Pavel Begunkov


      reply	other threads:[~2025-02-19 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 11:28 FAILED: patch "[PATCH] io_uring/kbuf: reallocate buf lists on upgrade" failed to apply to 6.13-stable tree gregkh
2025-02-19  1:28 ` [PATCH 6.12.y 6.13.y] io_uring/kbuf: reallocate buf lists on upgrade Pavel Begunkov
2025-02-19  1:30   ` Pavel Begunkov
2025-02-19  5:53     ` Greg KH
2025-02-19 12:13       ` Pavel Begunkov [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=f2f9e3ba-07fd-4fb0-ad05-893ef41a1a3f@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=pumpkin@devco.re \
    --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