Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: mst@redhat.com, jasowangio@gmail.com, xuanzhuo@linux.alibaba.com,
	eperezma@redhat.com, stefanha@redhat.com, sgarzare@redhat.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org,
	virtualization@lists.linux.dev, kvm@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	xmei5@asu.edu, bobbyeshleman@meta.com
Subject: Re: [PATCH v3 0/2] vsock/virtio: fix worker access after virtqueue teardown
Date: Mon, 03 Aug 2026 23:50:26 +0000	[thread overview]
Message-ID: <178580102614.2881314.2071869667851695934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1785352330.git.bestswngs@gmail.com>

Hello:

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

On Wed, 29 Jul 2026 12:16:53 -0700 you wrote:
> Virtio-vsock workers can remain queued while freeze deletes the
> virtqueues.  This series prevents workers delayed across freeze and
> restore from retaining pointers to deleted queues, and prevents the RX
> worker from refilling its queue after teardown.
> 
> Changes in v3:
> - Resend the series with proper email threading; no code changes.
> 
> [...]

Here is the summary with links:
  - [v3,1/2] vsock/virtio: read virtqueues under worker locks
    https://git.kernel.org/netdev/net/c/ebac8f6b1ef0
  - [v3,2/2] vsock/virtio: avoid refilling the RX queue after teardown
    https://git.kernel.org/netdev/net/c/a31e0ad44469

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



  parent reply	other threads:[~2026-08-03 23:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 18:58 [PATCH v2 0/2] vsock/virtio: fix worker access after virtqueue teardown Weiming Shi
2026-07-29 19:16 ` [PATCH v3 " Weiming Shi
2026-07-29 19:16   ` [PATCH v3 1/2] vsock/virtio: read virtqueues under worker locks Weiming Shi
2026-07-30 21:46     ` Bobby Eshleman
2026-07-29 19:16   ` [PATCH v3 2/2] vsock/virtio: avoid refilling the RX queue after teardown Weiming Shi
2026-07-30 19:17     ` sashiko-bot
2026-07-30 21:46     ` Bobby Eshleman
2026-08-03 23:50   ` patchwork-bot+netdevbpf [this message]
2026-08-04  9:45   ` [PATCH v3 0/2] vsock/virtio: fix worker access after virtqueue teardown 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=178580102614.2881314.2071869667851695934.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bestswngs@gmail.com \
    --cc=bobbyeshleman@meta.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=horms@kernel.org \
    --cc=jasowangio@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xmei5@asu.edu \
    --cc=xuanzhuo@linux.alibaba.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