All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexandru Matei <alexandru.matei@uipath.com>
Cc: stefanha@redhat.com, sgarzare@redhat.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	mihai.petrisor@uipath.com, viorel.canja@uipath.com
Subject: Re: [PATCH v4] vsock/virtio: initialize the_virtio_vsock before using VQs
Date: Wed, 25 Oct 2023 23:00:24 +0000	[thread overview]
Message-ID: <169827482432.1442.13189880459066041057.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231024191742.14259-1-alexandru.matei@uipath.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 24 Oct 2023 22:17:42 +0300 you wrote:
> Once VQs are filled with empty buffers and we kick the host, it can send
> connection requests. If the_virtio_vsock is not initialized before,
> replies are silently dropped and do not reach the host.
> 
> virtio_transport_send_pkt() can queue packets once the_virtio_vsock is
> set, but they won't be processed until vsock->tx_run is set to true. We
> queue vsock->send_pkt_work when initialization finishes to send those
> packets queued earlier.
> 
> [...]

Here is the summary with links:
  - [v4] vsock/virtio: initialize the_virtio_vsock before using VQs
    https://git.kernel.org/netdev/net/c/53b08c498515

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-10-25 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 19:17 [PATCH v4] vsock/virtio: initialize the_virtio_vsock before using VQs Alexandru Matei
2023-10-25  8:33 ` Stefano Garzarella
2023-10-25  8:33   ` Stefano Garzarella
2023-10-25 23:00 ` patchwork-bot+netdevbpf [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=169827482432.1442.13189880459066041057.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandru.matei@uipath.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.petrisor@uipath.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=viorel.canja@uipath.com \
    --cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.