From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: sashal@kernel.org, dhowells@redhat.com, horms@kernel.org,
jaltman@auristor.com, kuba@kernel.org,
linux-afs@lists.infradead.org, marc.dionne@auristor.com,
stable@kernel.org, stable@vger.kernel.org
Subject: Re: Backport RXRPC for 6.1.y from 6.2
Date: Sun, 10 May 2026 18:17:38 +0200 [thread overview]
Message-ID: <2026051040-primary-anyway-9a79@gregkh> (raw)
In-Reply-To: <20260509200157.191683-1-guanwentao@uniontech.com>
On Sun, May 10, 2026 at 04:01:57AM +0800, Wentao Guan wrote:
> Hello All,
>
> FYI, I found the commit list from v6.1..v6.2 mainline, with the refactor RXRPC
> commit list, it will possible for v6.1.172 to clean apply for the becoming fix
> patches for AF_RXRPC in higher kernel version, but it a bit large...
Why is this needed? If you want this, please provide a working set of
patches properly submitted, along with the reasoning why you just don't
move to a newer kernel version. And do you really use the AFS
filesystem in a 6.1.y kernel tree? If so, why?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-10 16:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 12:07 FAILED: patch "[PATCH] rxrpc: Fix conn-level packet handling to unshare RESPONSE" failed to apply to 6.6-stable tree gregkh
2026-05-03 14:33 ` [PATCH 6.6.y] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets Sasha Levin
2026-05-08 8:31 ` [PATCH RFC 6.6] rxrpc: Fix potential UAF after skb_unshare() failure Wentao Guan
2026-05-08 8:57 ` Greg KH
2026-05-08 9:38 ` Wentao Guan
2026-05-08 21:11 ` Sasha Levin
2026-05-09 20:01 ` Backport RXRPC for 6.1.y from 6.2 Wentao Guan
2026-05-10 16:17 ` Greg KH [this message]
2026-05-10 16:36 ` Wentao Guan
2026-05-10 16:43 ` Greg KH
2026-05-10 17:25 ` Jeffrey E Altman
2026-05-10 17:41 ` Wentao Guan
2026-05-10 18:04 ` Jeffrey E Altman
2026-05-10 18:26 ` Wentao Guan
2026-05-10 18:38 ` Jeffrey E Altman
2026-05-10 20:21 ` Wentao Guan
2026-05-10 20:50 ` Jeffrey Altman
2026-05-10 21:47 ` Wentao Guan
2026-05-10 22:30 ` Wentao Guan
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=2026051040-primary-anyway-9a79@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dhowells@redhat.com \
--cc=guanwentao@uniontech.com \
--cc=horms@kernel.org \
--cc=jaltman@auristor.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=marc.dionne@auristor.com \
--cc=sashal@kernel.org \
--cc=stable@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.