From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, xuanzhuo@linux.alibaba.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
leonardi@redhat.com, davem@davemloft.net, qwerty@theori.io,
eperezma@redhat.com, mst@redhat.com, edumazet@google.com,
kvm@vger.kernel.org, pabeni@redhat.com, stefanha@redhat.com,
jasowang@redhat.com, horms@kernel.org, v4bel@theori.io,
kuba@kernel.org, mhal@rbox.co, virtualization@lists.linux.dev,
bobby.eshleman@bytedance.com
Subject: Re: [PATCH net v2 0/5] vsock: some fixes due to transport de-assignment
Date: Tue, 14 Jan 2025 11:50:32 +0000 [thread overview]
Message-ID: <173685543253.4153435.8360593210112873590.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250110083511.30419-1-sgarzare@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 10 Jan 2025 09:35:06 +0100 you wrote:
> v1: https://lore.kernel.org/netdev/20250108180617.154053-1-sgarzare@redhat.com/
> v2:
> - Added patch 3 to cancel the virtio close delayed work when de-assigning
> the transport
> - Added patch 4 to clean the socket state after de-assigning the transport
> - Added patch 5 as suggested by Michael and Hyunwoo Kim. It's based on
> Hyunwoo Kim and Wongi Lee patch [1] but using WARN_ON and covering more
> functions
> - Added R-b/T-b tags
>
> [...]
Here is the summary with links:
- [net,v2,1/5] vsock/virtio: discard packets if the transport changes
https://git.kernel.org/netdev/net/c/2cb7c756f605
- [net,v2,2/5] vsock/bpf: return early if transport is not assigned
https://git.kernel.org/netdev/net/c/f6abafcd32f9
- [net,v2,3/5] vsock/virtio: cancel close work in the destructor
https://git.kernel.org/netdev/net/c/df137da9d6d1
- [net,v2,4/5] vsock: reset socket state when de-assigning the transport
https://git.kernel.org/netdev/net/c/a24009bc9be6
- [net,v2,5/5] vsock: prevent null-ptr-deref in vsock_*[has_data|has_space]
https://git.kernel.org/netdev/net/c/91751e248256
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:[~2025-01-14 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 8:35 [PATCH net v2 0/5] vsock: some fixes due to transport de-assignment Stefano Garzarella
2025-01-10 8:35 ` [PATCH net v2 1/5] vsock/virtio: discard packets if the transport changes Stefano Garzarella
2025-01-10 22:46 ` Hyunwoo Kim
2025-01-12 22:42 ` Michal Luczaj
2025-01-13 8:57 ` Stefano Garzarella
2025-01-13 9:07 ` Stefano Garzarella
2025-01-13 10:12 ` Michal Luczaj
2025-01-13 11:05 ` Stefano Garzarella
2025-01-13 13:51 ` Michal Luczaj
2025-01-13 15:01 ` Stefano Garzarella
2025-01-14 0:09 ` Michal Luczaj
2025-01-14 10:16 ` Stefano Garzarella
2025-01-14 16:31 ` Michal Luczaj
2025-01-16 8:57 ` Stefano Garzarella
2025-01-17 22:02 ` Michal Luczaj
2025-01-10 8:35 ` [PATCH net v2 2/5] vsock/bpf: return early if transport is not assigned Stefano Garzarella
2025-01-10 8:35 ` [PATCH net v2 3/5] vsock/virtio: cancel close work in the destructor Stefano Garzarella
2025-01-10 10:57 ` Luigi Leonardi
2025-01-10 22:48 ` Hyunwoo Kim
2025-01-10 8:35 ` [PATCH net v2 4/5] vsock: reset socket state when de-assigning the transport Stefano Garzarella
2025-01-10 10:56 ` Luigi Leonardi
2025-01-10 11:25 ` Stefano Garzarella
2025-01-10 8:35 ` [PATCH net v2 5/5] vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] Stefano Garzarella
2025-01-10 9:49 ` Luigi Leonardi
2025-01-10 22:52 ` Hyunwoo Kim
2025-01-14 11:50 ` 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=173685543253.4153435.8360593210112873590.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobby.eshleman@bytedance.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leonardi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qwerty@theori.io \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=v4bel@theori.io \
--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 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).