From: "Tomáš Golembiovský" <tgolembi@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] Fixes to qemu-nbd (--offset/--image-size)
Date: Tue, 20 Sep 2016 11:36:54 +0200 [thread overview]
Message-ID: <20160920113654.73d4a77a@fiorina> (raw)
The two patches basically "fix" the usage of --offset in qemu-nbd.
The first patch fixes the issue that when offset is used the device size
is not updated and the client may request read/write beyond the end of
the file.
Second patch adds new argument --image-size to hard set the size of the
device. This is useful in combination with --offset when the image is
embedded in a file, but does not span to the end of the file.
Tomáš Golembiovský (2):
qemu-nbd: Shrink image size by specified offset
qemu-nbd: Add --image-size option
qemu-nbd.c | 43 ++++++++++++++++++++++++++++++++++++++-----
qemu-nbd.texi | 4 ++++
2 files changed, 42 insertions(+), 5 deletions(-)
--
2.9.3
reply other threads:[~2016-09-20 9:41 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=20160920113654.73d4a77a@fiorina \
--to=tgolembi@redhat.com \
--cc=pbonzini@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).