Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Wentao Guan <guanwentao@uniontech.com>
To: jaltman@auristor.com
Cc: dhowells@redhat.com, gregkh@linuxfoundation.org,
	guanwentao@uniontech.com, horms@kernel.org, kuba@kernel.org,
	linux-afs@lists.infradead.org, marc.dionne@auristor.com,
	sashal@kernel.org, stable@kernel.org, stable@vger.kernel.org
Subject: Re: Backport RXRPC for 6.1.y from 6.2
Date: Mon, 11 May 2026 06:30:57 +0800	[thread overview]
Message-ID: <20260510223057.6945-1-guanwentao@uniontech.com> (raw)
In-Reply-To: <DA1B1E18-0F4E-4399-84AE-75EFD88713DE@auristor.com>

FYI, I am bisecting v6.1.73(poc fail) and v6.1.70(poc ok):
ac8c69e448f7e43586e102395844a117b0595031 is the first bad commit
commit ac8c69e448f7e43586e102395844a117b0595031 (HEAD)
Author: David Howells <dhowells@redhat.com>
Date:   Mon May 22 13:11:22 2023 +0100

    udp: Convert udp_sendpage() to use MSG_SPLICE_PAGES

    [ Upstream commit 7ac7c987850c3ec617c778f7bd871804dc1c648d ]

    Convert udp_sendpage() to use sendmsg() with MSG_SPLICE_PAGES rather than
    directly splicing in the pages itself.

    This allows ->sendpage() to be replaced by something that can handle
    multiple multipage folios in a single transaction.

    Signed-off-by: David Howells <dhowells@redhat.com>
    cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
    cc: David Ahern <dsahern@kernel.org>
    cc: Jens Axboe <axboe@kernel.dk>
    cc: Matthew Wilcox <willy@infradead.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Stable-dep-of: a0002127cd74 ("udp: move udp->no_check6_tx to udp->udp_flags")
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 net/ipv4/udp.c | 51 ++++++---------------------------------------------
 1 file changed, 6 insertions(+), 45 deletions(-)
so if the 6.1.y kernel convert to full MSG_SPLICE_PAGES will be vulnerable.

BRs
Wentao Guan

      parent reply	other threads:[~2026-05-10 22:33 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
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 [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=20260510223057.6945-1-guanwentao@uniontech.com \
    --to=guanwentao@uniontech.com \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox