[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a62124ba-bb3e-bd19-e2b4-50e8cb1465ea@tessares.net>
Date: Mon, 7 Sep 2020 17:07:33 +0200
From: Matthieu Baerts <matthieu.baerts@...sares.net>
To: Geliang Tang <geliangtang@...il.com>
Cc: Mat Martineau <mathew.j.martineau@...ux.intel.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
mptcp@...ts.01.org, linux-kernel@...r.kernel.org
Subject: Re: [MPTCP][PATCH net 2/2] mptcp: fix subflow's remote_id issues
Hi Geliang,
On 07/09/2020 12:29, Geliang Tang wrote:
> This patch set the init remote_id to zero, otherwise it will be a random
> number.
>
> Then it added the missing subflow's remote_id setting code both in
> __mptcp_subflow_connect and in subflow_ulp_clone.
Thank you for this other patch!
Here as well, may you add a "Fixes:" tag please?
(...)
> diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> index dc2c57860d2d..255695221309 100644
> --- a/net/mptcp/pm_netlink.c
> +++ b/net/mptcp/pm_netlink.c
> @@ -186,7 +186,7 @@ static void mptcp_pm_create_subflow_or_signal_addr(struct mptcp_sock *msk)
> {
> struct sock *sk = (struct sock *)msk;
> struct mptcp_pm_addr_entry *local;
> - struct mptcp_addr_info remote;
> + struct mptcp_addr_info remote = { 0 };
To respect the "reversed Xmas tree" way to declare variables, may you
move this line up to be the first one in the list please?
The rest looks good to me, thank you!
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
Powered by blists - more mailing lists