From: Jiyong Park <jiyong@google.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
adelva@google.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost/vsock: reset only the h2g connections upon release
Date: Thu, 10 Mar 2022 21:01:18 +0900 [thread overview]
Message-ID: <CALeUXe5bVk5P9s-4YFVtUtrvWBYRMmtMrx+BOv4AMHVn1Kvv=A@mail.gmail.com> (raw)
In-Reply-To: <20220310110036.fgy323c4hvk3mziq@sgarzare-redhat>
> I see your point, and it makes sense to keep KMI on stable branches, but
> mainline I would like to have the proposed approach since all transports
> use it to cycle on their sockets.
>
> So we could do a series with 2 patches:
> - Patch 1 fixes the problem in all transports by checking the transport
> in the callback (here we insert the fixes tag so we backport it to the
> stable branches)
> - Patch 2 moves the check in vsock_for_each_connected_socket() removing
> it from callbacks so it is less prone to errors and we merge it only
> mainline
>
> What do you think?
>
> Thanks,
> Stefano
>
That sounds like a plan. Will submit a new series soon.
prev parent reply other threads:[~2022-03-10 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 8:18 [PATCH] vhost/vsock: reset only the h2g connections upon release Jiyong Park
2022-03-10 8:59 ` Stefano Garzarella
2022-03-10 10:41 ` Jiyong Park
2022-03-10 11:00 ` Stefano Garzarella
2022-03-10 12:01 ` Jiyong Park [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='CALeUXe5bVk5P9s-4YFVtUtrvWBYRMmtMrx+BOv4AMHVn1Kvv=A@mail.gmail.com' \
--to=jiyong@google.com \
--cc=adelva@google.com \
--cc=jasowang@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).