From: Ziyang Xuan <william.xuanziyang@huawei.com>
To: <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
<davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
<yoshfuji@linux-ipv6.org>, <dsahern@kernel.org>,
<kuba@kernel.org>, <kuniyu@amazon.com>
Cc: <netdev@vger.kernel.org>
Subject: [PATCH 5.10 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification
Date: Thu, 20 Apr 2023 11:23:17 +0800 [thread overview]
Message-ID: <cover.1681952486.git.william.xuanziyang@huawei.com> (raw)
5.10 LTS has backported commit ca43ccf41224 ("dccp/tcp: Avoid negative
sk_forward_alloc by ipv6_pinfo.pktoptions.") and commit 62ec33b44e0f ("net:
Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues()."),
but these are incomplete. There are some patches that have not been
backported including key pre-patches commit d38afeec26ed ("tcp/udp:
Call inet6_destroy_sock() in IPv6 sk->sk_destruct().") and commit
b5fc29233d28 ("inet6: Remove inet6_destroy_sock() in
sk->sk_prot->destroy()."). Without them, there are some memory leak bugs.
Backport complete patchset for inet6_destroy_sock() call modification.
Kuniyuki Iwashima (5):
udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM).
tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct().
inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy().
dccp: Call inet6_destroy_sock() via sk->sk_destruct().
sctp: Call inet6_destroy_sock() via sk->sk_destruct().
include/net/ipv6.h | 2 ++
include/net/udp.h | 2 +-
include/net/udplite.h | 8 --------
net/dccp/dccp.h | 1 +
net/dccp/ipv6.c | 15 ++++++++-------
net/dccp/proto.c | 8 +++++++-
net/ipv4/udp.c | 9 ++++++---
net/ipv4/udplite.c | 8 ++++++++
net/ipv6/af_inet6.c | 15 ++++++++++++++-
net/ipv6/ipv6_sockglue.c | 20 ++++++++------------
net/ipv6/ping.c | 6 ------
net/ipv6/raw.c | 2 --
net/ipv6/tcp_ipv6.c | 8 +-------
net/ipv6/udp.c | 17 ++++++++++++++---
net/ipv6/udp_impl.h | 1 +
net/ipv6/udplite.c | 9 ++++++++-
net/l2tp/l2tp_ip6.c | 2 --
net/mptcp/protocol.c | 7 -------
net/sctp/socket.c | 29 +++++++++++++++++++++--------
19 files changed, 100 insertions(+), 69 deletions(-)
--
2.25.1
next reply other threads:[~2023-04-20 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 3:23 Ziyang Xuan [this message]
2023-04-20 3:23 ` [PATCH 5.10 1/5] udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM) Ziyang Xuan
2023-04-20 3:23 ` [PATCH 5.10 2/5] tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct() Ziyang Xuan
2023-04-20 3:23 ` [PATCH 5.10 3/5] inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy() Ziyang Xuan
2023-04-20 3:23 ` [PATCH 5.10 4/5] dccp: Call inet6_destroy_sock() via sk->sk_destruct() Ziyang Xuan
2023-04-20 3:23 ` [PATCH 5.10 5/5] sctp: " Ziyang Xuan
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=cover.1681952486.git.william.xuanziyang@huawei.com \
--to=william.xuanziyang@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).