From: Wentao Guan <guanwentao@uniontech.com>
To: harshit.m.mogalapalli@oracle.com
Cc: dhowells@redhat.com, gregkh@linuxfoundation.org,
guanwentao@uniontech.com, horms@kernel.org, imv4bel@gmail.com,
jaltman@auristor.com, jiayuan.chen@linux.dev, kuba@kernel.org,
linux-afs@lists.infradead.org, marc.dionne@auristor.com,
stable@kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: Re: [PATCH 6.12.y v3 1/2] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets
Date: Mon, 11 May 2026 16:16:19 +0800 [thread overview]
Message-ID: <20260511081619.65091-1-guanwentao@uniontech.com> (raw)
In-Reply-To: <a194c1df-8e39-48b9-a8f5-696e32558bad@oracle.com>
> On 11/05/26 13:11, Wentao Guan wrote:
> > [Readd rxrpc_skb_put_response_copy which missed in 016725807ce3 in v6.12.86]
> > Stable-dep-of: aa54b1d27fe0 ("rxrpc: Also unshare DATA/RESPONSE packets when
> > paged frags are present")
> Yes, I noticed this too.
Well
> But you got the commit wrong I think: (you probably meant)
Thanks, i paste wrong commit here, which i reported in
https://lore.kernel.org/stable/20260508083142.1752208-1-guanwentao@uniontech.com/
SUMMARY:
commit ("rxrpc: Fix potential UAF after skb_unshare() failure"):
bf20f46d94f1db38e6ffc0ca204a5fe0de01b495 v6.12
1f2740150f904bfa60e4bad74d65add3ccb5e7f8 upstream
is different
> Hence Wentao needs to add rxrpc_skb_put_response_copy() in this backport.
Yeah.
BRs
Wentao Guan
next prev parent reply other threads:[~2026-05-11 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 6:02 FAILED: patch "[PATCH] rxrpc: Also unshare DATA/RESPONSE packets when paged frags" failed to apply to 6.12-stable tree gregkh
2026-05-11 7:18 ` [PATCH 1/2] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets Wentao Guan
2026-05-11 7:18 ` [PATCH 2/2] rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present Wentao Guan
2026-05-11 7:27 ` [PATCH 6.12 v2 1/2] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets Wentao Guan
2026-05-11 7:28 ` [PATCH 6.12 v2 2/2] rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present Wentao Guan
2026-05-11 7:28 ` [PATCH " Greg KH
2026-05-11 7:33 ` Re: [PATCH 1/2] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets Wentao Guan
2026-05-11 7:39 ` Greg KH
2026-05-11 7:41 ` [PATCH 6.12.y v3 " Wentao Guan
2026-05-11 8:03 ` Harshit Mogalapalli
2026-05-11 8:16 ` Wentao Guan [this message]
2026-05-12 0:17 ` Sasha Levin
2026-05-12 2:04 ` Wentao Guan
2026-05-11 7:41 ` [PATCH 6.12.y v3 2/2] rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present Wentao Guan
2026-05-11 7:43 ` [PATCH 1/2] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets Wentao Guan
2026-05-11 7:28 ` Greg KH
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=20260511081619.65091-1-guanwentao@uniontech.com \
--to=guanwentao@uniontech.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=horms@kernel.org \
--cc=imv4bel@gmail.com \
--cc=jaltman@auristor.com \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=marc.dionne@auristor.com \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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