From: patchwork-bot+netdevbpf@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: stefanha@redhat.com, sgarzare@redhat.com, mst@redhat.com,
jasowangio@gmail.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
asias@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] vsock/virtio: flush works in dependency order
Date: Tue, 25 Aug 2026 10:40:08 +0000 [thread overview]
Message-ID: <178765440842.3381513.12080866327704897722.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260822164556.3750959-1-nicoyip.dev@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 23 Aug 2026 00:45:56 +0800 you wrote:
> virtio_vsock_remove() stops the virtqueues and then flushes each work
> item before freeing the enclosing virtio_vsock. The current order does
> not account for dependencies between those items: tx_work may queue
> send_pkt_work, and send_pkt_work may queue rx_work.
>
> In particular, send_pkt_work can set restart_rx and release tx_lock.
> The remove path can then stop the queues and flush rx_work before
> send_pkt_work queues it. Although the later send_pkt_work flush waits
> for that producer to finish, nothing waits for the newly queued rx_work,
> so kfree(vsock) can race with it.
>
> [...]
Here is the summary with links:
- [net] vsock/virtio: flush works in dependency order
https://git.kernel.org/netdev/net/c/728836ebca23
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-25 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 16:45 [PATCH net] vsock/virtio: flush works in dependency order Chengfeng Ye
2026-08-25 10:40 ` 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=178765440842.3381513.12080866327704897722.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asias@redhat.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=nicoyip.dev@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--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 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.