netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Popov <alex.popov@linux.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Jorgen Hansen <jhansen@vmware.com>,
	Stefan Schmidt <stefan@datenfreihafen.org>,
	Jeff Vander Stoep <jeffv@google.com>, Greg KH <greg@kroah.com>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] vsock: fix the race conditions in multi-transport support
Date: Mon, 1 Feb 2021 11:52:26 +0300	[thread overview]
Message-ID: <81c0e04f-cf50-8101-b024-16cd8526bec4@linux.com> (raw)
In-Reply-To: <20210201082643.zh3d7x7qzyf4hmfa@steredhat>

On 01.02.2021 11:26, Stefano Garzarella wrote:
> On Sun, Jan 31, 2021 at 01:59:14PM +0300, Alexander Popov wrote:
>> There are multiple similar bugs implicitly introduced by the
>> commit c0cfa2d8a788fcf4 ("vsock: add multi-transports support") and
>> commit 6a2c0962105ae8ce ("vsock: prevent transport modules unloading").
>>
>> The bug pattern:
>> [1] vsock_sock.transport pointer is copied to a local variable,
>> [2] lock_sock() is called,
>> [3] the local variable is used.
>> VSOCK multi-transport support introduced the race condition:
>> vsock_sock.transport value may change between [1] and [2].
>>
>> Let's copy vsock_sock.transport pointer to local variables after
>> the lock_sock() call.
> 
> We can add:
> 
> Fixes: c0cfa2d8a788 ("vsock: add multi-transports support")
> 
>>
>> Signed-off-by: Alexander Popov <alex.popov@linux.com>
>> ---
>> net/vmw_vsock/af_vsock.c | 17 ++++++++++++-----
>> 1 file changed, 12 insertions(+), 5 deletions(-)
>>
>> diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
>> index d10916ab4526..28edac1f9aa6 100644
>> --- a/net/vmw_vsock/af_vsock.c
>> +++ b/net/vmw_vsock/af_vsock.c
>> @@ -997,9 +997,12 @@ static __poll_t vsock_poll(struct file *file, struct socket *sock,
>> 			mask |= EPOLLOUT | EPOLLWRNORM | EPOLLWRBAND;
>>
>> 	} else if (sock->type == SOCK_STREAM) {
>> -		const struct vsock_transport *transport = vsk->transport;
>> +		const struct vsock_transport *transport = NULL;
> 
> I think we can avoid initializing to NULL since we assign it shortly 
> after.
> 
>> +
>> 		lock_sock(sk);
>>
>> +		transport = vsk->transport;
>> +
>> 		/* Listening sockets that have connections in their accept
>> 		 * queue can be read.
>> 		 */
>> @@ -1082,10 +1085,11 @@ static int vsock_dgram_sendmsg(struct socket *sock, struct msghdr *msg,
>> 	err = 0;
>> 	sk = sock->sk;
>> 	vsk = vsock_sk(sk);
>> -	transport = vsk->transport;
>>
>> 	lock_sock(sk);
>>
>> +	transport = vsk->transport;
>> +
>> 	err = vsock_auto_bind(vsk);
>> 	if (err)
>> 		goto out;
>> @@ -1544,10 +1548,11 @@ static int vsock_stream_setsockopt(struct 
>> socket *sock,
>> 	err = 0;
>> 	sk = sock->sk;
>> 	vsk = vsock_sk(sk);
>> -	transport = vsk->transport;
>>
>> 	lock_sock(sk);
>>
>> +	transport = vsk->transport;
>> +
>> 	switch (optname) {
>> 	case SO_VM_SOCKETS_BUFFER_SIZE:
>> 		COPY_IN(val);
>> @@ -1680,7 +1685,6 @@ static int vsock_stream_sendmsg(struct socket *sock, struct msghdr *msg,
>>
>> 	sk = sock->sk;
>> 	vsk = vsock_sk(sk);
>> -	transport = vsk->transport;
>> 	total_written = 0;
>> 	err = 0;
>>
>> @@ -1689,6 +1693,8 @@ static int vsock_stream_sendmsg(struct socket *sock, struct msghdr *msg,
>>
>> 	lock_sock(sk);
>>
>> +	transport = vsk->transport;
>> +
>> 	/* Callers should not provide a destination with stream sockets. */
>> 	if (msg->msg_namelen) {
>> 		err = sk->sk_state == TCP_ESTABLISHED ? -EISCONN : -EOPNOTSUPP;
>> @@ -1823,11 +1829,12 @@ vsock_stream_recvmsg(struct socket *sock, struct msghdr *msg, size_t len,
>>
>> 	sk = sock->sk;
>> 	vsk = vsock_sk(sk);
>> -	transport = vsk->transport;
>> 	err = 0;
>>
>> 	lock_sock(sk);
>>
>> +	transport = vsk->transport;
>> +
>> 	if (!transport || sk->sk_state != TCP_ESTABLISHED) {
>> 		/* Recvmsg is supposed to return 0 if a peer performs an
>> 		 * orderly shutdown. Differentiate between that case and when a
>> -- 
>> 2.26.2
>>
> 
> Thanks for fixing this issues. With the small changes applied:
> 
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>

Hello Stefano,

Thanks for the review.

I've just sent the v2.

Best regards,
Alexander

      reply	other threads:[~2021-02-01  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210131105914.2217229-1-alex.popov@linux.com>
2021-01-31 19:27 ` [PATCH 1/1] vsock: fix the race conditions in multi-transport support Linus Torvalds
2021-02-01  8:26 ` Stefano Garzarella
2021-02-01  8:52   ` Alexander Popov [this message]

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=81c0e04f-cf50-8101-b024-16cd8526bec4@linux.com \
    --to=alex.popov@linux.com \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=jeffv@google.com \
    --cc=jhansen@vmware.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefan@datenfreihafen.org \
    --cc=torvalds@linuxfoundation.org \
    /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).