qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paul Brook <paul@codesourcery.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu list <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL] virtio-serial: Fixes, flow control
Date: Mon, 24 Jan 2011 11:58:07 +0530	[thread overview]
Message-ID: <20110124062807.GB9376@amit-x200.redhat.com> (raw)

Hello,

Please pull for fixes to the virtio-serial code:
- Don't copy over guest buffer to host (prevents potential DoS
  scenarios, pointed out by Paul Brook)
- Add support for flow control
- A couple of trivial fixes to virtio-console code

The patches were sent out to the list on 19 Jan 2011, subject
"[PATCH 0/7] virtio-serial: Don't copy guest buf to host, flow control"

The following changes since commit
b646968336d4180bdd7d2e24209708dcee6ba400:

  checkpatch: adjust to QEMUisms (2011-01-20 20:58:56 +0000)

are available in the git repository at:
  git://git.kernel.org/pub/scm/virt/qemu/amit/virtio-serial.git
for-anthony

Amit Shah (7):
      virtio-console: Factor out common init between console and generic ports
      virtio-console: Remove unnecessary braces
      virtio-serial: move out discard logic in a separate function
      virtio-serial: Don't copy over guest buffer to host
      virtio-serial: Let virtio-serial-bus know if all data was consumed
      virtio-serial: Add support for flow control
      virtio-serial: save/restore new fields in port struct

 hw/virtio-console.c    |   38 +++++++--------
 hw/virtio-serial-bus.c |  123
+++++++++++++++++++++++++++++++++++++++---------
 hw/virtio-serial.h     |   24 ++++++++-
 3 files changed, 139 insertions(+), 46 deletions(-)


		Amit

                 reply	other threads:[~2011-01-24  6:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110124062807.GB9376@amit-x200.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=paul@codesourcery.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).