[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdcb307f-d2a8-4aef-bb7d-dd87e56ff740@linux.ibm.com>
Date: Thu, 12 Oct 2023 21:04:11 +0200
From: Wenjia Zhang <wenjia@...ux.ibm.com>
To: "D. Wythe" <alibuda@...ux.alibaba.com>, kgraul@...ux.ibm.com,
jaka@...ux.ibm.com, wintera@...ux.ibm.com
Cc: kuba@...nel.org, davem@...emloft.net, netdev@...r.kernel.org,
linux-s390@...r.kernel.org, linux-rdma@...r.kernel.org
Subject: Re: [PATCH net 5/5] net/smc: put sk reference if close work was
canceled
On 11.10.23 09:33, D. Wythe wrote:
> From: "D. Wythe" <alibuda@...ux.alibaba.com>
>
> Note that we always hold a reference to sock when attempting
> to submit close_work.
yes
Therefore, if we have successfully
> canceled close_work from pending, we MUST release that reference
> to avoid potential leaks.
>
Isn't the corresponding reference already released inside the
smc_close_passive_work()?
> Fixes: 42bfba9eaa33 ("net/smc: immediate termination for SMCD link groups")
> Signed-off-by: D. Wythe <alibuda@...ux.alibaba.com>
> ---
> net/smc/smc_close.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/smc/smc_close.c b/net/smc/smc_close.c
> index 449ef45..10219f5 100644
> --- a/net/smc/smc_close.c
> +++ b/net/smc/smc_close.c
> @@ -116,7 +116,8 @@ static void smc_close_cancel_work(struct smc_sock *smc)
> struct sock *sk = &smc->sk;
>
> release_sock(sk);
> - cancel_work_sync(&smc->conn.close_work);
> + if (cancel_work_sync(&smc->conn.close_work))
> + sock_put(sk);
> cancel_delayed_work_sync(&smc->conn.tx_work);
> lock_sock(sk);
> }
Powered by blists - more mailing lists