From: Peter Xu <peterx@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 9/9] chardev: tcp: postpone TLS work until machine done
Date: Thu, 8 Mar 2018 21:55:22 +0800 [thread overview]
Message-ID: <20180308135521.GH32252@xz-mi> (raw)
In-Reply-To: <20180308133143.GP4718@redhat.com>
On Thu, Mar 08, 2018 at 01:31:43PM +0000, Daniel P. Berrangé wrote:
> On Thu, Mar 08, 2018 at 07:42:13PM +0800, Peter Xu wrote:
> > On Thu, Mar 08, 2018 at 10:13:59AM +0000, Daniel P. Berrangé wrote:
> > > On Thu, Mar 08, 2018 at 11:44:09AM +0800, Peter Xu wrote:
> > > > On Wed, Mar 07, 2018 at 12:36:50PM +0000, Daniel P. Berrangé wrote:
> > > >
> > > > [...]
> > > >
> > > > > > diff --git a/chardev/char-socket.c b/chardev/char-socket.c
> > > > > > index bd40864f87..997c70dd7d 100644
> > > > > > --- a/chardev/char-socket.c
> > > > > > +++ b/chardev/char-socket.c
> > > > > > @@ -31,6 +31,7 @@
> > > > > > #include "qemu/option.h"
> > > > > > #include "qapi/error.h"
> > > > > > #include "qapi/clone-visitor.h"
> > > > > > +#include "sysemu/sysemu.h"
> > > > > >
> > > > > > #include "chardev/char-io.h"
> > > > > >
> > > > > > @@ -722,6 +723,11 @@ static void tcp_chr_tls_init(Chardev *chr)
> > > > > > Error *err = NULL;
> > > > > > gchar *name;
> > > > > >
> > > > > > + if (!machine_init_done) {
> > > > > > + /* This will be postponed to machine_done notifier */
> > > > > > + return;
> > > > > > + }
> > > > > > +
> > > > > > if (s->is_listen) {
> > > > > > tioc = qio_channel_tls_new_server(
> > > > > > s->ioc, s->tls_creds,
> > > > > > @@ -1145,6 +1151,10 @@ static int tcp_chr_machine_done_hook(Chardev *chr)
> > > > > > tcp_chr_connect_async(chr);
> > > > > > }
> > > > > >
> > > > > > + if (s->tls_creds) {
> > > > > > + tcp_chr_tls_init(chr);
> > > > > > + }
> > > > >
> > > > > This looks questionable - AFAICT, there's no guarantee we have any
> > > > > client connection active when the machine dnoe hook runs. Only if
> > > > > the chardev is set in client mode, and reconnect_time is *not* set,
> > > > > but this seems to be run unconditionally.
> > > >
> > > > You are right. Thanks for spotting that.
> > > >
> > > > Then how about this? It's a bit ugly, but I think it should be safe:
> > >
> > > Is it perhaps not possible to just check if 's->ioc' is non-NULL
> > > in the tcp_chr_machine_done_hook for your original patch ?
> >
> > In tcp_chr_new_client() I see that s->ioc will be set no matter what,
> > and that function can even be called without TLS enabled I think.
> > Does that mean only check against s->ioc would not be enough?
>
> I mean like this:
>
> diff --git a/chardev/char-socket.c b/chardev/char-socket.c
> index a1966aae51..19e3193817 100644
> --- a/chardev/char-socket.c
> +++ b/chardev/char-socket.c
> @@ -723,6 +723,11 @@ static void tcp_chr_tls_init(Chardev *chr)
> Error *err = NULL;
> gchar *name;
>
> + if (!machine_init_done) {
> + /* This will be postponed to machine_done notifier */
> + return;
> + }
> +
> if (s->is_listen) {
> tioc = qio_channel_tls_new_server(
> s->ioc, s->tls_creds,
> @@ -1146,6 +1151,10 @@ static int tcp_chr_machine_done_hook(Chardev *chr)
> tcp_chr_connect_async(chr);
> }
>
> + if (s->ioc && s->tls_creds) {
> + tcp_chr_tls_init(chr);
> + }
> +
> return 0;
> }
>
>
>
> s->ioc will only be != NULL, if some codepath in qemu_chr_parse_socket
I guess here you mean qmp_chardev_open_socket().
> ended up calling tcp_chr_new_client(). If that happened we will have
> skipped setup of TLS, so calling tcp_chr_tls_init() based on
> s->ioc && s->tls_creds feels right to me.
Yes, it looks right to me too. :)
I'll post a complete patch soon with your authorship.
Thanks!
--
Peter Xu
next prev parent reply other threads:[~2018-03-08 13:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 5:33 [Qemu-devel] [PATCH v2 0/9] chardev: qio related non-default context support Peter Xu
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 1/9] vl: export machine_init_done Peter Xu
2018-03-07 12:21 ` Daniel P. Berrangé
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 2/9] chardev: fix leak in tcp_chr_telnet_init_io() Peter Xu
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 3/9] chardev: update net listener gcontext Peter Xu
2018-03-07 12:26 ` Daniel P. Berrangé
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 4/9] chardev: allow telnet gsource to switch gcontext Peter Xu
2018-03-07 12:28 ` Daniel P. Berrangé
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 5/9] chardev: introduce chr_machine_done hook Peter Xu
2018-03-07 12:30 ` Daniel P. Berrangé
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 6/9] chardev: use chardev's gcontext for async connect Peter Xu
2018-03-07 12:31 ` Daniel P. Berrangé
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 7/9] chardev: tcp: postpone async connection setup Peter Xu
2018-03-07 12:32 ` Daniel P. Berrangé
2018-08-16 17:49 ` Marc-André Lureau
2018-08-16 18:27 ` Marc-André Lureau
2018-08-17 5:31 ` Peter Xu
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 8/9] chardev: tcp: let TLS run on chardev context Peter Xu
2018-03-07 12:33 ` Daniel P. Berrangé
2018-03-06 5:33 ` [Qemu-devel] [PATCH v2 9/9] chardev: tcp: postpone TLS work until machine done Peter Xu
2018-03-07 12:36 ` Daniel P. Berrangé
2018-03-07 12:40 ` Daniel P. Berrangé
2018-03-07 15:06 ` Paolo Bonzini
2018-03-08 5:10 ` Peter Xu
2018-03-08 3:44 ` Peter Xu
2018-03-08 10:13 ` Daniel P. Berrangé
2018-03-08 11:42 ` Peter Xu
2018-03-08 13:31 ` Daniel P. Berrangé
2018-03-08 13:55 ` Peter Xu [this message]
2018-03-08 14:07 ` [Qemu-devel] [PATCH v2.1 " Peter Xu
2018-03-07 11:30 ` [Qemu-devel] [PATCH v2 0/9] chardev: qio related non-default context support Stefan Hajnoczi
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=20180308135521.GH32252@xz-mi \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).