From: Thomas Huth <thuth@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2] test: Fix test-crypto-secret when compiling without keyring support
Date: Tue, 11 Apr 2023 12:16:26 +0200 [thread overview]
Message-ID: <849e915d-8628-9bd1-1b6b-9861027fcd3a@redhat.com> (raw)
In-Reply-To: <20230411095156.6500-1-quintela@redhat.com>
On 11/04/2023 11.51, Juan Quintela wrote:
> Linux keyring support is protected by CONFIG_KEYUTILS.
> We also need CONFIG_SECRET_KEYRING.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
>
> ---
>
> - Previous version of this patch changed the meson build rules.
> Daniel told me that the proper fix was to change the #ifdef test.
>
> - Change rule again. We need both defines.
> - Now it passes the test with and without CONFIG_SECRET_KEYRING defined
>
> ---
> tests/unit/test-crypto-secret.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/unit/test-crypto-secret.c b/tests/unit/test-crypto-secret.c
> index 34a4aecc12..d31d97f36a 100644
> --- a/tests/unit/test-crypto-secret.c
> +++ b/tests/unit/test-crypto-secret.c
> @@ -24,7 +24,7 @@
> #include "crypto/secret.h"
> #include "qapi/error.h"
> #include "qemu/module.h"
> -#ifdef CONFIG_KEYUTILS
> +#if defined(CONFIG_KEYUTILS) && defined(CONFIG_SECRET_KEYRING)
> #include "crypto/secret_keyring.h"
> #include <keyutils.h>
> #endif
> @@ -128,7 +128,7 @@ static void test_secret_indirect_emptyfile(void)
> g_free(fname);
> }
>
> -#ifdef CONFIG_KEYUTILS
> +#if defined(CONFIG_KEYUTILS) && defined(CONFIG_SECRET_KEYRING)
>
> #define DESCRIPTION "qemu_test_secret"
> #define PAYLOAD "Test Payload"
> @@ -268,7 +268,7 @@ static void test_secret_keyring_bad_key_access_right(void)
> keyctl_unlink(key, KEY_SPEC_PROCESS_KEYRING);
> }
>
> -#endif /* CONFIG_KEYUTILS */
> +#endif /* CONFIG_KEYUTILS && CONFIG_SECRET_KEYRING */
>
> static void test_secret_noconv_base64_good(void)
> {
> @@ -571,7 +571,7 @@ int main(int argc, char **argv)
> g_test_add_func("/crypto/secret/indirect/emptyfile",
> test_secret_indirect_emptyfile);
>
> -#ifdef CONFIG_KEYUTILS
> +#if defined(CONFIG_KEYUTILS) && defined(CONFIG_SECRET_KEYRING)
> g_test_add_func("/crypto/secret/keyring/good",
> test_secret_keyring_good);
> g_test_add_func("/crypto/secret/keyring/revoked_key",
> @@ -582,7 +582,7 @@ int main(int argc, char **argv)
> test_secret_keyring_bad_serial_key);
> g_test_add_func("/crypto/secret/keyring/bad_key_access_right",
> test_secret_keyring_bad_key_access_right);
> -#endif /* CONFIG_KEYUTILS */
> +#endif /* CONFIG_SECRET_KEYRING */
Nit: The comment after the "#endif" should mention both switches now, like
the one earlier in the patch.
Thomas
next prev parent reply other threads:[~2023-04-11 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 9:51 [PATCH v2] test: Fix test-crypto-secret when compiling without keyring support Juan Quintela
2023-04-11 10:16 ` Thomas Huth [this message]
2023-04-14 11:43 ` Juan Quintela
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=849e915d-8628-9bd1-1b6b-9861027fcd3a@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).