All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>,
	dhowells@redhat.com, guanwentao@uniontech.com, imv4bel@gmail.com,
	jiayuan.chen@linux.dev, stable@vger.kernel.org,
	torvalds@linux-foundation.org,
	Marc Dionne <marc.dionne@auristor.com>,
	Jeffrey Altman <jaltman@auristor.com>,
	Simon Horman <horms@kernel.org>,
	linux-afs@lists.infradead.org, stable@kernel.org,
	Jakub Kicinski <kuba@kernel.org>,
	Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: [PATCH 6.12.y v3 1/2] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets
Date: Mon, 11 May 2026 20:17:54 -0400	[thread overview]
Message-ID: <20260511220000.stable-reply-item003@kernel.org> (raw)
In-Reply-To: <20260511074104.60836-1-guanwentao@uniontech.com>

On Mon, May 11, 2026 at 03:41:04PM +0800, Wentao Guan wrote:
> (cherry picked from commit 24481a7f573305706054c59e275371f8d0fe919f)
> [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")

Queued for 6.12 (both 1/2 and 2/2), thanks.

I fixed up the bracket annotation at apply time per Harshit's review:
the trace event was actually dropped in bf20f46d94f1 ("rxrpc: Fix
potential UAF after skb_unshare() failure"), not 016725807ce3, so the
queued changelog references bf20f46d94f1.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2026-05-12  0:18 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
2026-05-12  0:17             ` Sasha Levin [this message]
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=20260511220000.stable-reply-item003@kernel.org \
    --to=sashal@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guanwentao@uniontech.com \
    --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 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.