From: Stefano Garzarella <sgarzare@redhat.com>
To: Norbert Slusarek <nslusarek@gmx.net>
Cc: kuba@kernel.org, alex.popov@linux.com, eric.dumazet@gmail.com,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] net/vmw_vsock: improve locking in vsock_connect_timeout()
Date: Fri, 5 Feb 2021 18:19:51 +0100 [thread overview]
Message-ID: <20210205171951.emlq5t5fuiwtpse3@steredhat> (raw)
In-Reply-To: <trinity-f8e0937a-cf0e-4d80-a76e-d9a958ba3ef1-1612535522360@3c-app-gmx-bap12>
On Fri, Feb 05, 2021 at 03:32:02PM +0100, Norbert Slusarek wrote:
>From: Norbert Slusarek <nslusarek@gmx.net>
>Date: Fri, 5 Feb 2021 13:14:05 +0100
>Subject: [PATCH] net/vmw_vsock: improve locking in vsock_connect_timeout()
>
>A possible locking issue in vsock_connect_timeout() was recognized by
>Eric Dumazet which might cause a null pointer dereference in
>vsock_transport_cancel_pkt(). This patch assures that
>vsock_transport_cancel_pkt() will be called within the lock, so a race
>condition won't occur which could result in vsk->transport to be set to NULL.
>
>Fixes: 380feae0def7 ("vsock: cancel packets when failing to connect")
I have a doubt about the tag to use, since until we introduced
transports in commit c0cfa2d8a788 ("vsock: add multi-transports
support") this issue didn't cause many problems.
But it must be said that in the commit 380feae0def7 ("vsock: cancel
packets when failing to connect") the vsock_transport_cancel_pkt() was
called with the lock held in vsock_stream_connect() and without lock in
vsock_connect_timeout(), so maybe this tag is okay.
Anyway, the patch LGTM:
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
>Reported-by: Eric Dumazet <eric.dumazet@gmail.com>
>Signed-off-by: Norbert Slusarek <nslusarek@gmx.net>
>---
> net/vmw_vsock/af_vsock.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
>diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
>index 6894f21dc147..ad7dd9d93b5b 100644
>--- a/net/vmw_vsock/af_vsock.c
>+++ b/net/vmw_vsock/af_vsock.c
>@@ -1243,7 +1243,6 @@ static void vsock_connect_timeout(struct work_struct *work)
> {
> struct sock *sk;
> struct vsock_sock *vsk;
>- int cancel = 0;
>
> vsk = container_of(work, struct vsock_sock, connect_work.work);
> sk = sk_vsock(vsk);
>@@ -1254,11 +1253,9 @@ static void vsock_connect_timeout(struct work_struct *work)
> sk->sk_state = TCP_CLOSE;
> sk->sk_err = ETIMEDOUT;
> sk->sk_error_report(sk);
>- cancel = 1;
>+ vsock_transport_cancel_pkt(vsk);
> }
> release_sock(sk);
>- if (cancel)
>- vsock_transport_cancel_pkt(vsk);
>
> sock_put(sk);
> }
>--
>2.30.0
>
next prev parent reply other threads:[~2021-02-05 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 14:32 [PATCH] net/vmw_vsock: improve locking in vsock_connect_timeout() Norbert Slusarek
2021-02-05 17:19 ` Stefano Garzarella [this message]
2021-02-07 0:56 ` Jakub Kicinski
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=20210205171951.emlq5t5fuiwtpse3@steredhat \
--to=sgarzare@redhat.com \
--cc=alex.popov@linux.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nslusarek@gmx.net \
/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