From: Kishen Maloor <kishen.maloor@intel.com>
To: kishen.maloor@intel.com, mptcp@lists.linux.dev
Subject: [PATCH mptcp-next v2 0/3] mptcp: fix bug in userspace PM APIs
Date: Wed, 20 Apr 2022 00:25:21 -0400 [thread overview]
Message-ID: <20220420042524.2268380-1-kishen.maloor@intel.com> (raw)
This series fixes issue #267:
https://github.com/multipath-tcp/mptcp_net-next/issues/267
Specifically, calls to mptcp_token_get_sock() from userspace PM APIs
hold a reference to the msk which needs to be freed before leaving those
functions. This was causing a memory leak which was caught in
the CI debug build.
v2:
-Fixed code style.
Kishen Maloor (3):
Squash-to: mptcp: netlink: Add MPTCP_PM_CMD_ANNOUNCE
Squash-to: mptcp: netlink: Add MPTCP_PM_CMD_REMOVE
Squash-to: mptcp: netlink: allow userspace-driven subflow
establishment
net/mptcp/pm_userspace.c | 93 +++++++++++++++++++++++-----------------
1 file changed, 53 insertions(+), 40 deletions(-)
base-commit: e561667a821b0ecccba582520829f38da50567a3
--
2.31.1
next reply other threads:[~2022-04-20 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 4:25 Kishen Maloor [this message]
2022-04-20 4:25 ` [PATCH mptcp-next v2 1/3] Squash-to: mptcp: netlink: Add MPTCP_PM_CMD_ANNOUNCE Kishen Maloor
2022-04-20 4:25 ` [PATCH mptcp-next v2 2/3] Squash-to: mptcp: netlink: Add MPTCP_PM_CMD_REMOVE Kishen Maloor
2022-04-20 4:25 ` [PATCH mptcp-next v2 3/3] Squash-to: mptcp: netlink: allow userspace-driven subflow establishment Kishen Maloor
2022-04-20 6:17 ` Squash-to: mptcp: netlink: allow userspace-driven subflow establishment: Tests Results MPTCP CI
2022-04-20 15:22 ` [PATCH mptcp-next v2 0/3] mptcp: fix bug in userspace PM APIs Matthieu Baerts
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=20220420042524.2268380-1-kishen.maloor@intel.com \
--to=kishen.maloor@intel.com \
--cc=mptcp@lists.linux.dev \
/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