stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: stable@vger.kernel.org, Muhammad Ramdhan <ramdhan@starlabs.sg>,
	Bing-Jhong Billy Jheng <billy@starlabs.sg>,
	Jacob Soo <jacob.soo@starlabs.sg>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH stable-6.6 0/3] provided buffer recycling fixes
Date: Tue, 11 Feb 2025 11:18:30 +0100	[thread overview]
Message-ID: <2025021100-demote-graph-fdeb@gregkh> (raw)
In-Reply-To: <cover.1738772087.git.asml.silence@gmail.com>

On Mon, Feb 10, 2025 at 03:21:35PM +0000, Pavel Begunkov wrote:
> Fixes for the provided buffers for not allowing kbufs to cross a single
> execution section. Upstream had most of it already fixed by chance,
> which is why all 3 patches refer to a single upstream commit.

Ah.  Ok, that makes more sense, nevermind, I should have read patch 0/X
first...

I'll drop the upstream commit reference here as it's just confusing.

thanks,

greg k-h

  parent reply	other threads:[~2025-02-11 10:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 15:21 [PATCH stable-6.6 0/3] provided buffer recycling fixes Pavel Begunkov
2025-02-10 15:21 ` [PATCH stable-6.6 1/3] io_uring: fix multishots with selected buffers Pavel Begunkov
2025-02-11 10:16   ` Greg KH
2025-02-10 15:21 ` [PATCH stable-6.6 2/3] io_uring: fix io_req_prep_async with provided buffers Pavel Begunkov
2025-02-11 10:17   ` Greg KH
2025-02-10 15:21 ` [PATCH stable-6.6 3/3] io_uring/rw: commit provided buffer state on async Pavel Begunkov
2025-02-11 10:16   ` Greg KH
2025-02-11 10:18 ` Greg KH [this message]
2025-02-12 11:59   ` [PATCH stable-6.6 0/3] provided buffer recycling fixes 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=2025021100-demote-graph-fdeb@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=billy@starlabs.sg \
    --cc=jacob.soo@starlabs.sg \
    --cc=ramdhan@starlabs.sg \
    --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;
as well as URLs for NNTP newsgroup(s).