From: Peter Wu <peter@lekensteyn.nl>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-trivial@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/dmg: make it modular if using additional library
Date: Tue, 10 Mar 2015 10:10:49 +0100 [thread overview]
Message-ID: <20150310091049.GE23387@al> (raw)
In-Reply-To: <1425971164-9845-1-git-send-email-mjt@msgid.tls.msk.ru>
On Tue, Mar 10, 2015 at 10:06:04AM +0300, Michael Tokarev wrote:
> block/dmg can use additional library (libbz2) to read
> bzip2-compressed files. Make the block driver to be
> a module if libbz2 support is requested, to avoid extra
> library dependency by default.
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Tested-by: Peter Wu <peter@lekensteyn.nl>
Reviewed-by: Peter Wu <peter@lekensteyn.nl>
> --
>
> This might be questionable, to make the thing to be either
> module or built-in depending on build environment, so a
> better idea may be to make it modular unconditionally.
> This block device format isn't used often.
I do not mind making it a module unconditionally, that would make it
easier to disable should a security bug come around the corner.
Kind regards,
Peter
> block/Makefile.objs | 3 ++-
> configure | 3 +++
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/block/Makefile.objs b/block/Makefile.objs
> index db2933e..440c51f 100644
> --- a/block/Makefile.objs
> +++ b/block/Makefile.objs
> @@ -1,7 +1,8 @@
> -block-obj-y += raw_bsd.o qcow.o vdi.o vmdk.o cloop.o dmg.o bochs.o vpc.o vvfat.o
> +block-obj-y += raw_bsd.o qcow.o vdi.o vmdk.o cloop.o bochs.o vpc.o vvfat.o
> block-obj-y += qcow2.o qcow2-refcount.o qcow2-cluster.o qcow2-snapshot.o qcow2-cache.o
> block-obj-y += qed.o qed-gencb.o qed-l2-cache.o qed-table.o qed-cluster.o
> block-obj-y += qed-check.o
> +block-obj-$(CONFIG_DMG) += dmg.o
> block-obj-$(CONFIG_VHDX) += vhdx.o vhdx-endian.o vhdx-log.o
> block-obj-$(CONFIG_QUORUM) += quorum.o
> block-obj-y += parallels.o blkdebug.o blkverify.o
> diff --git a/configure b/configure
> index 7ba4bcb..1dd5721 100755
> --- a/configure
> +++ b/configure
> @@ -4772,6 +4772,9 @@ fi
> if test "$bzip2" = "yes" ; then
> echo "CONFIG_BZIP2=y" >> $config_host_mak
> echo "BZIP2_LIBS=-lbz2" >> $config_host_mak
> + echo "CONFIG_DMG=m" >> $config_host_mak
> +else
> + echo "CONFIG_DMG=y" >> $config_host_mak
> fi
>
> if test "$libiscsi" = "yes" ; then
> --
> 2.1.4
>
next prev parent reply other threads:[~2015-03-10 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 7:06 [Qemu-devel] [PATCH] block/dmg: make it modular if using additional library Michael Tokarev
2015-03-10 8:50 ` Kevin Wolf
2015-03-10 9:17 ` Fam Zheng
2015-03-10 10:09 ` Kevin Wolf
2015-03-10 13:24 ` Markus Armbruster
2015-03-10 13:31 ` Michael Tokarev
2015-03-10 13:59 ` Kevin Wolf
2015-03-10 13:58 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-03-10 14:01 ` Michael Tokarev
2015-03-10 14:07 ` Kevin Wolf
2015-03-10 14:38 ` [Qemu-devel] " Michael Tokarev
2015-03-11 13:17 ` Stefan Hajnoczi
2015-03-11 13:06 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-03-10 9:10 ` Peter Wu [this message]
2015-03-11 13:23 ` [Qemu-devel] " Stefan Hajnoczi
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=20150310091049.GE23387@al \
--to=peter@lekensteyn.nl \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).