From: Xin Long <lucien.xin@gmail.com>
To: stable@vger.kernel.org, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
sashal@kernel.org, gregkh@linuxfoundation.org
Subject: [PATCH linux-4.14.y 0/2] sctp: fix a memory leak
Date: Mon, 04 Nov 2019 05:16:24 +0000 [thread overview]
Message-ID: <cover.1572844054.git.lucien.xin@gmail.com> (raw)
These 2 patches are missed in linux-4.14.y, it will cause crash
when commit 63dfb7938b13 ("sctp: change sctp_prot .no_autobind
with true") is backported only.
Conflicts:
- Context difference in Patch 1/2 due to the lack of
Commit c981f254cc82.
Xin Long (2):
sctp: fix the issue that flags are ignored when using kernel_connect
sctp: not bind the socket in sctp_connect
include/net/sctp/sctp.h | 2 ++
net/sctp/ipv6.c | 2 +-
net/sctp/protocol.c | 2 +-
net/sctp/socket.c | 55 ++++++++++++++++++++++++++-----------------------
4 files changed, 33 insertions(+), 28 deletions(-)
--
2.1.0
WARNING: multiple messages have this Message-ID (diff)
From: Xin Long <lucien.xin@gmail.com>
To: stable@vger.kernel.org, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
sashal@kernel.org, gregkh@linuxfoundation.org
Subject: [PATCH linux-4.14.y 0/2] sctp: fix a memory leak
Date: Mon, 4 Nov 2019 13:16:24 +0800 [thread overview]
Message-ID: <cover.1572844054.git.lucien.xin@gmail.com> (raw)
These 2 patches are missed in linux-4.14.y, it will cause crash
when commit 63dfb7938b13 ("sctp: change sctp_prot .no_autobind
with true") is backported only.
Conflicts:
- Context difference in Patch 1/2 due to the lack of
Commit c981f254cc82.
Xin Long (2):
sctp: fix the issue that flags are ignored when using kernel_connect
sctp: not bind the socket in sctp_connect
include/net/sctp/sctp.h | 2 ++
net/sctp/ipv6.c | 2 +-
net/sctp/protocol.c | 2 +-
net/sctp/socket.c | 55 ++++++++++++++++++++++++++-----------------------
4 files changed, 33 insertions(+), 28 deletions(-)
--
2.1.0
next reply other threads:[~2019-11-04 5:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 5:16 Xin Long [this message]
2019-11-04 5:16 ` [PATCH linux-4.14.y 0/2] sctp: fix a memory leak Xin Long
2019-11-04 5:16 ` [PATCH linux-4.14.y 1/2] sctp: fix the issue that flags are ignored when using kernel_connect Xin Long
2019-11-04 5:16 ` Xin Long
2019-11-04 5:16 ` [PATCH linux-4.14.y 2/2] sctp: not bind the socket in sctp_connect Xin Long
2019-11-04 5:16 ` Xin Long
2019-11-04 10:57 ` [PATCH linux-4.14.y 0/2] sctp: fix a memory leak Greg KH
2019-11-04 10:57 ` 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=cover.1572844054.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=nhorman@tuxdriver.com \
--cc=sashal@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.