From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Joanne Koong <joannelkoong@gmail.com>,
stable@vger.kernel.org, clm@meta.com
Subject: Re: [PATCH] io_uring/rsrc: clean up buffer cloning arg validation (for 6.18-stable tree)
Date: Tue, 24 Feb 2026 16:54:08 -0800 [thread overview]
Message-ID: <2026022403-latter-wow-3f07@gregkh> (raw)
In-Reply-To: <ee96be6b-f0d9-479c-8ab1-f8c7e04ccdeb@kernel.dk>
On Sun, Feb 22, 2026 at 08:33:24AM -0700, Jens Axboe wrote:
> On 2/20/26 11:19 AM, Joanne Koong wrote:
> > Commit id upstream: b8201b50e403815f941d1c6581a27fdbfe7d0fd4
> > ("io_uring/rsrc: clean up buffer cloning arg validation")
> > Link to the patch:
> > https://lore.kernel.org/io-uring/20251204215116.2642044-1-joannelkoong@gmail.com/#t
> > Kernel version to apply it to: 6.18-stable tree
> >
> > Hi stable@,
> >
> > Chris Mason recently detected that this patch is a required dependency
> > for commit 5b804b8f1e0d ("io_uring/rsrc: fix lost entries after cloned
> > range") in the 6.18-stable tree [1]. Without this patch, the changes
> > in commit 5b804b8f1e0d use an incorrect value for nbufs when it
> > assigns "i = nbufs" [2].
> >
> > Could you please apply this patch to the 6.18-stable tree as a
> > dependency fix needed for commit 5b804b8f1e0d?
> >
> > Thanks,
> > Joanne
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.18.y&id=5b804b8f1e0d66413774d43f7a4b78bba0ca6272
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/io_uring/rsrc.c?h=linux-6.18.y#n1252.
>
> FWIW, this is approved on my end. CC Greg.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2026-02-25 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 18:19 [PATCH] io_uring/rsrc: clean up buffer cloning arg validation (for 6.18-stable tree) Joanne Koong
2026-02-22 15:33 ` Jens Axboe
2026-02-25 0:54 ` Greg Kroah-Hartman [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=2026022403-latter-wow-3f07@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=clm@meta.com \
--cc=joannelkoong@gmail.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