qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Greg Kurz <groug@kaod.org>
Subject: [Qemu-devel] [PULL 0/2] 9pfs fixes for 2.9 2017-03-28
Date: Tue, 28 Mar 2017 10:46:32 +0200	[thread overview]
Message-ID: <1490690794-19023-1-git-send-email-groug@kaod.org> (raw)

The following changes since commit eb06c9e2d3c8f026a206e8402b0ffa201060ec8e:

  Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-03-27 17:34:50 +0100)

are available in the git repository at:

  https://github.com/gkurz/qemu.git tags/for-upstream

for you to fetch changes up to 34ef723ce34aaa14f94530c06a0ab3170a19bb59:

  tests/virtio-9p-test: Don't call le*_to_cpus on fields of packed struct (2017-03-27 21:15:31 +0200)

----------------------------------------------------------------
This series fixes potential memory/fd leaks in 9pfs and a crash when
running tests/virtio-9p-test on SPARC hosts.

----------------------------------------------------------------
Li Qiang (1):
      9pfs: fix file descriptor leak

Peter Maydell (1):
      tests/virtio-9p-test: Don't call le*_to_cpus on fields of packed struct

 hw/9pfs/9p.c           | 8 ++++++++
 tests/virtio-9p-test.c | 4 ++--
 2 files changed, 10 insertions(+), 2 deletions(-)
-- 
2.7.4

             reply	other threads:[~2017-03-28  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  8:46 Greg Kurz [this message]
2017-03-28  8:46 ` [Qemu-devel] [PULL 1/2] 9pfs: fix file descriptor leak Greg Kurz
2017-03-28  8:46 ` [Qemu-devel] [PULL 2/2] tests/virtio-9p-test: Don't call le*_to_cpus on fields of packed struct Greg Kurz
2017-03-28  9:41 ` [Qemu-devel] [PULL 0/2] 9pfs fixes for 2.9 2017-03-28 Peter Maydell

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=1490690794-19023-1-git-send-email-groug@kaod.org \
    --to=groug@kaod.org \
    --cc=peter.maydell@linaro.org \
    --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).