All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: dhowells@redhat.com, horms@kernel.org, jaltman@auristor.com,
	kuba@kernel.org, linux-afs@lists.infradead.org,
	marc.dionne@auristor.com, sashal@kernel.org, stable@kernel.org,
	stable@vger.kernel.org
Subject: Re: Re: Backport RXRPC for 6.1.y from 6.2
Date: Sun, 10 May 2026 18:43:23 +0200	[thread overview]
Message-ID: <2026051004-dreamless-dab-f7b0@gregkh> (raw)
In-Reply-To: <20260510163636.260801-1-guanwentao@uniontech.com>

On Mon, May 11, 2026 at 12:36:36AM +0800, Wentao Guan wrote:
> > 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?
> 
> FYI, there are bugfixes such as ("rxrpc: Fix conn-level packet handling to unshare RESPONSE packets")
> affect the 6.1.y kernel, and the final goal is clean apply fixes for CVE-2026-43500 such as
> ("rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present") in maillist.

That was not stated here at all, so we had no context :(

If you need/want those bugfixes, great!  Provide a patch series of them
and we will be glad to review them.

> > move to a newer kernel version.  And do you really use the AFS
> > filesystem in a 6.1.y kernel tree?  If so, why?
> NO, just affected by compiled kernel which enabled the config:(,
> we are preparing fix such as disable AFS and AF_RXRPC or fix it...

Great, if you don't need this, disable it and then you don't need the
backports either :)

thanks,

greg k-h

  reply	other threads:[~2026-05-10 16:44 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
2026-05-10 16:36           ` Wentao Guan
2026-05-10 16:43             ` Greg KH [this message]
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=2026051004-dreamless-dab-f7b0@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.