netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Junnan Wu <junnan01.wu@samsung.com>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
	eperezma@redhat.com, horms@kernel.org, jasowang@redhat.com,
	kuba@kernel.org, kvm@vger.kernel.org, lei19.wang@samsung.com,
	linux-kernel@vger.kernel.org, mst@redhat.com,
	netdev@vger.kernel.org, pabeni@redhat.com, q1.huang@samsung.com,
	stefanha@redhat.com, virtualization@lists.linux.dev,
	xuanzhuo@linux.alibaba.com, ying01.gao@samsung.com,
	ying123.xu@samsung.com
Subject: Re: [Patch net v3] vsock/virtio: fix variables initialization during resuming
Date: Sat, 15 Feb 2025 04:00:36 +0000	[thread overview]
Message-ID: <173959203625.2185212.746025659708481674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250214012200.1883896-1-junnan01.wu@samsung.com>

Hello:

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

On Fri, 14 Feb 2025 09:22:00 +0800 you wrote:
> When executing suspend to ram twice in a row,
> the `rx_buf_nr` and `rx_buf_max_nr` increase to three times vq->num_free.
> Then after virtqueue_get_buf and `rx_buf_nr` decreased
> in function virtio_transport_rx_work,
> the condition to fill rx buffer
> (rx_buf_nr < rx_buf_max_nr / 2) will never be met.
> 
> [...]

Here is the summary with links:
  - [net,v3] vsock/virtio: fix variables initialization during resuming
    https://git.kernel.org/netdev/net/c/55eff109e76a

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



  parent reply	other threads:[~2025-02-15  4:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250211071930epcas5p2dbb3a4171fbe04574c0fa7b3a6f1a0c2@epcas5p2.samsung.com>
2025-02-11  7:19 ` [Patch net 0/2] vsock suspend/resume fix Junnan Wu
2025-02-11  7:19   ` [Patch net 1/2] vsock/virtio: initialize rx_buf_nr and rx_buf_max_nr when resuming Junnan Wu
2025-02-11  8:57     ` Stefano Garzarella
2025-02-13  1:28       ` Junnan Wu
2025-02-13  9:25         ` Stefano Garzarella
2025-02-13 14:47           ` Stefano Garzarella
2025-02-14  1:02             ` Junnan Wu
2025-02-14  1:22             ` [Patch net v3] vsock/virtio: fix variables initialization during resuming Junnan Wu
2025-02-14  9:13               ` Luigi Leonardi
2025-02-14 12:17               ` Michael S. Tsirkin
2025-02-14 13:34               ` Stefano Garzarella
2025-02-15  4:00               ` patchwork-bot+netdevbpf [this message]
2025-02-11  7:19   ` [Patch net 2/2] vsock/virtio: Don't reset the created SOCKET during suspend to ram Junnan Wu
2025-02-11  8:49     ` Stefano Garzarella
2025-02-15 14:26     ` Markus Elfring
2025-02-11  8:54   ` [Patch net 0/2] vsock suspend/resume fix Stefano Garzarella

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=173959203625.2185212.746025659708481674.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=horms@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=junnan01.wu@samsung.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lei19.wang@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=q1.huang@samsung.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=ying01.gao@samsung.com \
    --cc=ying123.xu@samsung.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).