From: Kishen Maloor <kishen.maloor@intel.com>
To: kishen.maloor@intel.com, mptcp@lists.linux.dev
Subject: [PATCH mptcp-next 0/3] mptcp: fix bug in userspace PM APIs
Date: Tue, 19 Apr 2022 19:03:37 -0400 [thread overview]
Message-ID: <20220419230340.2263545-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.
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-19 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 23:03 Kishen Maloor [this message]
2022-04-19 23:03 ` [PATCH mptcp-next 1/3] Squash-to: mptcp: netlink: Add MPTCP_PM_CMD_ANNOUNCE Kishen Maloor
2022-04-20 1:04 ` Geliang Tang
2022-04-19 23:03 ` [PATCH mptcp-next 2/3] Squash-to: mptcp: netlink: Add MPTCP_PM_CMD_REMOVE Kishen Maloor
2022-04-19 23:03 ` [PATCH mptcp-next 3/3] Squash-to: mptcp: netlink: allow userspace-driven subflow establishment Kishen Maloor
2022-04-20 1:02 ` Squash-to: mptcp: netlink: allow userspace-driven subflow establishment: Tests Results MPTCP CI
2022-04-19 23:22 ` [PATCH mptcp-next 0/3] mptcp: fix bug in userspace PM APIs Mat Martineau
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=20220419230340.2263545-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 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.