qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/4] Convert chardevs to QIOChannel & add TLS support
Date: Tue, 19 Jan 2016 14:14:13 +0100	[thread overview]
Message-ID: <569E36A5.7030501@redhat.com> (raw)
In-Reply-To: <1453202071-10289-1-git-send-email-berrange@redhat.com>

On 19/01/2016 12:14, Daniel P. Berrange wrote:
> This is an update of patches previously shown in an RFC posting
> 
>   RFC: https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00829.html
>    v1: https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg04222.html
>    v2: https://lists.gnu.org/archive/html/qemu-devel/2015-12/msg03823.html
>    v3: https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg01601.html
> 
> This short series converts the chardev backends to use the new
> QIOChannel framework. After doing so it then adds support for
> TLS encryption of TCP chardevs. The commit message in the last
> patch explains the TLS encryption in detail.
> 
> The GIOChannel -> QIOChannel conversion has been validated by
> running the qtest framework, which indeed found a few bugs
> initially which I have since fixed.
> 
> The TLS support has been tested for interoperability using
> the gnutls-serv and gnutls-client programs which provide
> stub TLS endpoints/clients respectively.
> 
> Changed in v4:
> 
>  - Rebase to resolve conflicts with recent merged patches

Thanks, this looks good!

Paolo

> Changed in v3:
> 
>  - Fix buffer update after partial send of telnet data
> 
> Daniel P. Berrange (4):
>   char: remove fixed length filename allocation
>   char: convert from GIOChannel to QIOChannel
>   char: don't assume telnet initialization will not block
>   char: introduce support for TLS encrypted TCP chardev backend
> 
>  qapi-schema.json |   2 +
>  qemu-char.c      | 913 ++++++++++++++++++++++++++++---------------------------
>  qemu-options.hx  |   9 +-
>  tests/Makefile   |   2 +-
>  4 files changed, 479 insertions(+), 447 deletions(-)
> 

      parent reply	other threads:[~2016-01-19 13:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 11:14 [Qemu-devel] [PATCH v4 0/4] Convert chardevs to QIOChannel & add TLS support Daniel P. Berrange
2016-01-19 11:14 ` [Qemu-devel] [PATCH v4 1/4] char: remove fixed length filename allocation Daniel P. Berrange
2016-01-19 11:14 ` [Qemu-devel] [PATCH v4 2/4] char: convert from GIOChannel to QIOChannel Daniel P. Berrange
2016-03-18 16:43   ` Laurent Vivier
2016-03-18 16:56     ` Daniel P. Berrange
2016-03-18 17:10       ` Laurent Vivier
2016-01-19 11:14 ` [Qemu-devel] [PATCH v4 3/4] char: don't assume telnet initialization will not block Daniel P. Berrange
2016-01-19 11:14 ` [Qemu-devel] [PATCH v4 4/4] char: introduce support for TLS encrypted TCP chardev backend Daniel P. Berrange
2016-01-19 13:14 ` Paolo Bonzini [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=569E36A5.7030501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.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).