qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: [Qemu-devel] [PULL 0/4] 2.12 post-release NBD fixes, 2018-05-04
Date: Fri,  4 May 2018 08:30:30 -0500	[thread overview]
Message-ID: <20180504133034.1328397-1-eblake@redhat.com> (raw)

The following changes since commit 26bd8d98c4b3284a4c6fe3b67c98b1edd00e9beb:

  Merge remote-tracking branch 'remotes/vivier/tags/m68k-for-2.13-pull-request' into staging (2018-05-01 15:26:06 +0100)

are available in the Git repository at:

  git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2018-05-04

for you to fetch changes up to acfd8f7a5f92e703d2d046cbe3d510008a697194:

  nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply (2018-05-04 08:23:39 -0500)

Fix various issues with NBD in 2.12, some found by Coverity, and some by
implementation interoperability testing.

And May the Fourth be with you

----------------------------------------------------------------
nbd patches for 2018-05-04

- Vladimir Sementsov-Ogievskiy: 0/2 fix coverity bugs
- Eric Blake: nbd/client: Fix error messages during NBD_INFO_BLOCK_SIZE
- Eric Blake: nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply

----------------------------------------------------------------
Eric Blake (2):
      nbd/client: Fix error messages during NBD_INFO_BLOCK_SIZE
      nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply

Vladimir Sementsov-Ogievskiy (2):
      nbd/client: fix nbd_negotiate_simple_meta_context
      migration/block-dirty-bitmap: fix memory leak in dirty_bitmap_load_bits

 block/nbd-client.c             | 10 +++++++---
 migration/block-dirty-bitmap.c |  1 +
 nbd/client.c                   | 18 ++++++++++++------
 3 files changed, 20 insertions(+), 9 deletions(-)

Eric Blake (2):
  nbd/client: Fix error messages during NBD_INFO_BLOCK_SIZE
  nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply

Vladimir Sementsov-Ogievskiy (2):
  nbd/client: fix nbd_negotiate_simple_meta_context
  migration/block-dirty-bitmap: fix memory leak in
    dirty_bitmap_load_bits

 block/nbd-client.c             | 10 +++++++---
 migration/block-dirty-bitmap.c |  1 +
 nbd/client.c                   | 18 ++++++++++++------
 3 files changed, 20 insertions(+), 9 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-05-04 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 13:30 Eric Blake [this message]
2018-05-04 13:30 ` [Qemu-devel] [PULL 1/4] nbd/client: fix nbd_negotiate_simple_meta_context Eric Blake
2018-05-04 13:30 ` [Qemu-devel] [PULL 2/4] migration/block-dirty-bitmap: fix memory leak in dirty_bitmap_load_bits Eric Blake
2018-05-04 13:30 ` [Qemu-devel] [PULL 3/4] nbd/client: Fix error messages during NBD_INFO_BLOCK_SIZE Eric Blake
2018-05-04 13:30 ` [Qemu-devel] [PULL 4/4] nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply Eric Blake
2018-05-04 14:44 ` [Qemu-devel] [PULL 0/4] 2.12 post-release NBD fixes, 2018-05-04 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=20180504133034.1328397-1-eblake@redhat.com \
    --to=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).