From: Hangyu Hua <hbh25y@gmail.com>
To: Tung Quang Nguyen <tung.q.nguyen@dektech.com.au>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jmaloy@redhat.com" <jmaloy@redhat.com>,
"ying.xue@windriver.com" <ying.xue@windriver.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"tgraf@suug.ch" <tgraf@suug.ch>
Subject: Re: [PATCH] net: tipc: fix possible refcount leak in tipc_sk_create()
Date: Wed, 29 Jun 2022 14:09:42 +0800 [thread overview]
Message-ID: <aee933e9-e07e-49df-94bf-a0ddea5da59e@gmail.com> (raw)
In-Reply-To: <DB9PR05MB9078334A4067BF8F84DF60D488BB9@DB9PR05MB9078.eurprd05.prod.outlook.com>
On 2022/6/29 11:49, Tung Quang Nguyen wrote:
>> sk need to be free when tipc_sk_insert fails. While tipc_sk_insert is hard
>> to fail, it's better to fix this.
> Incorrect English grammar. You should use a simple comment in changelog, for example: "Free sk in case tipc_sk_insert() fails."
Thanks a lot. I will fix this then send a v2.
Hangyu.
>>
>> Fixes: 07f6c4bc048a ("tipc: convert tipc reference table to use generic rhashtable")
>> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
>> ---
>> net/tipc/socket.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/net/tipc/socket.c b/net/tipc/socket.c
>> index 17f8c523e33b..43509c7e90fc 100644
>> --- a/net/tipc/socket.c
>> +++ b/net/tipc/socket.c
>> @@ -502,6 +502,7 @@ static int tipc_sk_create(struct net *net, struct socket *sock,
>> sock_init_data(sock, sk);
>> tipc_set_sk_state(sk, TIPC_OPEN);
>> if (tipc_sk_insert(tsk)) {
>> + sk_free(sk);
>> pr_warn("Socket create failed; port number exhausted\n");
>> return -EINVAL;
>> }
>> --
>> 2.25.1
>
next prev parent reply other threads:[~2022-06-29 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 2:24 [PATCH] net: tipc: fix possible refcount leak in tipc_sk_create() Hangyu Hua
2022-06-29 3:49 ` Tung Quang Nguyen
2022-06-29 6:09 ` Hangyu Hua [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-29 6:29 Hangyu Hua
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=aee933e9-e07e-49df-94bf-a0ddea5da59e@gmail.com \
--to=hbh25y@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tgraf@suug.ch \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
--cc=ying.xue@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).