From: David Miller <davem@davemloft.net>
To: sgarzare@redhat.com
Cc: jasowang@redhat.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
mst@redhat.com, stefanha@redhat.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] vsock/virtio: fixes about packet delivery to monitoring devices
Date: Mon, 27 Apr 2020 10:18:19 -0700 (PDT) [thread overview]
Message-ID: <20200427.101819.498317950218972559.davem@davemloft.net> (raw)
In-Reply-To: <20200424150830.183113-1-sgarzare@redhat.com>
From: Stefano Garzarella <sgarzare@redhat.com>
Date: Fri, 24 Apr 2020 17:08:28 +0200
> During the review of v1, Stefan pointed out an issue introduced by
> that patch, where replies can appear in the packet capture before
> the transmitted packet.
>
> While fixing my patch, reverting it and adding a new flag in
> 'struct virtio_vsock_pkt' (patch 2/2), I found that we already had
> that issue in vhost-vsock, so I fixed it (patch 1/2).
>
> v1 -> v2:
> - reverted the v1 patch, to avoid that replies can appear in the
> packet capture before the transmitted packet [Stefan]
> - added patch to fix packet delivering to monitoring devices in
> vhost-vsock
> - added patch to check if the packet is already delivered to
> monitoring devices
>
> v1: https://patchwork.ozlabs.org/project/netdev/patch/20200421092527.41651-1-sgarzare@redhat.com/
Series applied, thank you.
prev parent reply other threads:[~2020-04-27 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:08 Stefano Garzarella
2020-04-24 15:08 ` [PATCH net v2 1/2] vhost/vsock: fix packet delivery order " Stefano Garzarella
2020-04-24 15:08 ` [PATCH net v2 2/2] vsock/virtio: fix multiple packet delivery " Stefano Garzarella
2020-04-27 17:18 ` David Miller [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=20200427.101819.498317950218972559.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jasowang@redhat.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=sgarzare@redhat.com \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®