From: "Michael S. Tsirkin" <mst@redhat•com>
To: Jiyong Park <jiyong@google•com>
Cc: sgarzare@redhat•com, stefanha@redhat•com, jasowang@redhat•com,
davem@davemloft•net, kuba@kernel•org, adelva@google•com,
kvm@vger•kernel.org, virtualization@lists•linux-foundation.org,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH 0/2] vsock: cycle only on its own socket
Date: Thu, 10 Mar 2022 07:59:15 -0500 [thread overview]
Message-ID: <20220310075854-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220310075554-mutt-send-email-mst@kernel.org>
On Thu, Mar 10, 2022 at 07:57:58AM -0500, Michael S. Tsirkin wrote:
> On Thu, Mar 10, 2022 at 09:54:23PM +0900, Jiyong Park wrote:
> > Hi Stefano,
> >
> > As suggested [1], I've made two patches for easier backporting without
> > breaking KMI.
> >
> > PATCH 1 fixes the very issue of cycling all vsocks regardless of the
> > transport and shall be backported.
> >
> > PATCH 2 is a refactor of PATCH 1 that forces the filtering to all
> > (including future) uses of vsock_for_each_connected_socket.
> >
> > Thanks,
> >
> > [1] https://lore.kernel.org/lkml/20220310110036.fgy323c4hvk3mziq@sgarzare-redhat/
>
>
> OK that's better. Pls do include changelog in the future.
>
> Acked-by: Michael S. Tsirkin <mst@redhat•com>
Hmm actually I think I have a better idea. Hang on.
>
>
> > Jiyong Park (2):
> > vsock: each transport cycles only on its own sockets
> > vsock: refactor vsock_for_each_connected_socket
> >
> > drivers/vhost/vsock.c | 3 ++-
> > include/net/af_vsock.h | 3 ++-
> > net/vmw_vsock/af_vsock.c | 9 +++++++--
> > net/vmw_vsock/virtio_transport.c | 7 +++++--
> > net/vmw_vsock/vmci_transport.c | 3 ++-
> > 5 files changed, 18 insertions(+), 7 deletions(-)
> >
> >
> > base-commit: 3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b
> > --
> > 2.35.1.723.g4982287a31-goog
prev parent reply other threads:[~2022-03-10 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 12:54 [PATCH 0/2] vsock: cycle only on its own socket Jiyong Park
2022-03-10 12:54 ` [PATCH 1/2] vsock: each transport cycles only on its own sockets Jiyong Park
2022-03-10 13:01 ` Michael S. Tsirkin
2022-03-10 13:11 ` Jiyong Park
2022-03-10 13:16 ` Michael S. Tsirkin
2022-03-10 13:18 ` Stefano Garzarella
2022-03-11 2:55 ` kernel test robot
2022-03-10 12:54 ` [PATCH 2/2] vsock: refactor vsock_for_each_connected_socket Jiyong Park
2022-03-10 13:09 ` Michael S. Tsirkin
2022-03-10 12:57 ` [PATCH 0/2] vsock: cycle only on its own socket Michael S. Tsirkin
2022-03-10 12:59 ` Michael S. Tsirkin [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=20220310075854-mutt-send-email-mst@kernel.org \
--to=mst@redhat$(echo .)com \
--cc=adelva@google$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jasowang@redhat$(echo .)com \
--cc=jiyong@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sgarzare@redhat$(echo .)com \
--cc=stefanha@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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