2021-11-07 19:15:12

by Eiichi Tsukata

[permalink] [raw]
Subject: [PATCH net] vsock: prevent unnecessary refcnt inc for nonblocking connect

Currently vosck_connect() increments sock refcount for nonblocking
socket each time it's called, which can lead to memory leak if
it's called multiple times because connect timeout function decrements
sock refcount only once.

Fixes it by making vsock_connect() return -EALREADY immediately when
sock state is already SS_CONNECTING.

Signed-off-by: Eiichi Tsukata <[email protected]>
---
net/vmw_vsock/af_vsock.c | 2 ++
1 file changed, 2 insertions(+)

diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index 7d851eb3a683..ed0df839c38c 100644
--- a/net/vmw_vsock/af_vsock.c
+++ b/net/vmw_vsock/af_vsock.c
@@ -1322,6 +1322,8 @@ static int vsock_connect(struct socket *sock, struct sockaddr *addr,
* non-blocking call.
*/
err = -EALREADY;
+ if (flags & O_NONBLOCK)
+ goto out;
break;
default:
if ((sk->sk_state == TCP_LISTEN) ||
--
2.33.1


2021-11-08 10:18:03

by Stefano Garzarella

[permalink] [raw]
Subject: Re: [PATCH net] vsock: prevent unnecessary refcnt inc for nonblocking connect

On Sun, Nov 07, 2021 at 12:03:04PM +0000, Eiichi Tsukata wrote:
>Currently vosck_connect() increments sock refcount for nonblocking
>socket each time it's called, which can lead to memory leak if
>it's called multiple times because connect timeout function decrements
>sock refcount only once.
>
>Fixes it by making vsock_connect() return -EALREADY immediately when
>sock state is already SS_CONNECTING.
>
>Signed-off-by: Eiichi Tsukata <[email protected]>
>---
> net/vmw_vsock/af_vsock.c | 2 ++
> 1 file changed, 2 insertions(+)

Make sense to me, thanks for fixing this issue!
I think would be better to add the Fixes ref in the commit message:

Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")

With that:
Reviewed-by: Stefano Garzarella <[email protected]>

Thanks,
Stefano

2021-11-09 07:24:52

by Eiichi Tsukata

[permalink] [raw]
Subject: Re: [PATCH net] vsock: prevent unnecessary refcnt inc for nonblocking connect



> On Nov 8, 2021, at 17:30, Stefano Garzarella <[email protected]> wrote:
>
> On Sun, Nov 07, 2021 at 12:03:04PM +0000, Eiichi Tsukata wrote:
>> Currently vosck_connect() increments sock refcount for nonblocking
>> socket each time it's called, which can lead to memory leak if
>> it's called multiple times because connect timeout function decrements
>> sock refcount only once.
>>
>> Fixes it by making vsock_connect() return -EALREADY immediately when
>> sock state is already SS_CONNECTING.
>>
>> Signed-off-by: Eiichi Tsukata <[email protected]>
>> ---
>> net/vmw_vsock/af_vsock.c | 2 ++
>> 1 file changed, 2 insertions(+)
>
> Make sense to me, thanks for fixing this issue!
> I think would be better to add the Fixes ref in the commit message:
>
> Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")
>
> With that:
> Reviewed-by: Stefano Garzarella <[email protected]>
>
> Thanks,
> Stefano
>

Thanks for comments! I’ll add Fixes and Reviewed-by tag then send v2.

Eiichi