From: Fam Zheng <famz@redhat.com>
To: Sascha Silbe <silbe@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] quorum: Only compile when supported
Date: Tue, 5 Jul 2016 16:11:08 +0800 [thread overview]
Message-ID: <20160705081108.GD29307@ad.usersys.redhat.com> (raw)
In-Reply-To: <87k2h0ldni.fsf@oc4731375738.ibm.com>
On Tue, 07/05 09:58, Sascha Silbe wrote:
> Dear Fam (or Zheng?),
Hi Sascha,
Zheng is the last name here. :)
>
> Fam Zheng <famz@redhat.com> writes:
>
> > This was the only exceptional module init function that does something
> > else than a simple list of bdrv_register() calls, in all the block
> > drivers.
> >
> > The qcrypto_hash_supports is actually a static check, determined at
> > compile time. Follow the block-job-$(CONFIG_FOO) convention for
> > consistency.
>
> Good idea.
>
>
> [block/Makefile.objs]
> > @@ -3,7 +3,7 @@ block-obj-y += qcow2.o qcow2-refcount.o qcow2-cluster.o qcow2-snapshot.o qcow2-c
> > 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_VHDX) += vhdx.o vhdx-endian.o vhdx-log.o
> > -block-obj-y += quorum.o
> > +block-obj-$(CONFIG_GNUTLS_HASH) += quorum.o
> [...]
> [block/quorum.c]
> > static void bdrv_quorum_init(void)
> > {
> > - if (!qcrypto_hash_supports(QCRYPTO_HASH_ALG_SHA256)) {
> > - /* SHA256 hash support is required for quorum device */
> > - return;
> > - }
> > bdrv_register(&bdrv_quorum);
>
> The quorum driver needs SHA256 which was introduced in gnutls
> 2.11.1. However configure sets CONFIG_GNUTLS_HASH when gnutls 2.9.10+ is
> present. You should either bump the version in configure or add an
> explicit configure check for SHA256.
Yes, I just noticed commit 0c16c056a4f removed CONFIG_GNUTLS_HASH so I need to
rebase anyway (that commit also fixed this version requirement we have been
missing as you mentioned). Thanks for reviewing!
Fam
next prev parent reply other threads:[~2016-07-05 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 1:47 [Qemu-devel] [PATCH] quorum: Only compile when supported Fam Zheng
2016-06-28 8:17 ` Alberto Garcia
2016-07-02 12:36 ` Max Reitz
2016-07-04 11:43 ` Alberto Garcia
2016-07-05 7:03 ` Fam Zheng
2016-07-05 7:58 ` Sascha Silbe
2016-07-05 8:11 ` Fam Zheng [this message]
2016-07-05 8:20 ` Alberto Garcia
2016-07-05 9:15 ` Sascha Silbe
2016-07-05 8:45 ` Daniel P. Berrange
2016-07-05 8:57 ` Fam Zheng
2016-07-05 9:35 ` Daniel P. Berrange
2016-07-06 0:56 ` Fam Zheng
2016-07-05 9:18 ` Alberto Garcia
2016-07-05 9:26 ` Daniel P. Berrange
2016-07-05 10:05 ` Daniel P. Berrange
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=20160705081108.GD29307@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=silbe@linux.vnet.ibm.com \
/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).