From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: kvm: fix build with glibc >= 2.30
Date: Wed, 13 Nov 2019 15:48:11 +0100 [thread overview]
Message-ID: <f439dee6-012a-d9aa-5f16-cbd911d6d55d@redhat.com> (raw)
In-Reply-To: <20191113125115.23100-1-vkuznets@redhat.com>
On 13/11/19 13:51, Vitaly Kuznetsov wrote:
> Glibc-2.30 gained gettid() wrapper, selftests fail to compile:
>
> lib/assert.c:58:14: error: static declaration of ‘gettid’ follows non-static declaration
> 58 | static pid_t gettid(void)
> | ^~~~~~
> In file included from /usr/include/unistd.h:1170,
> from include/test_util.h:18,
> from lib/assert.c:10:
> /usr/include/bits/unistd_ext.h:34:16: note: previous declaration of ‘gettid’ was here
> 34 | extern __pid_t gettid (void) __THROW;
> | ^~~~~~
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> ---
> tools/testing/selftests/kvm/lib/assert.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/lib/assert.c b/tools/testing/selftests/kvm/lib/assert.c
> index 4911fc77d0f6..d1cf9f6e0e6b 100644
> --- a/tools/testing/selftests/kvm/lib/assert.c
> +++ b/tools/testing/selftests/kvm/lib/assert.c
> @@ -55,7 +55,7 @@ static void test_dump_stack(void)
> #pragma GCC diagnostic pop
> }
>
> -static pid_t gettid(void)
> +static pid_t _gettid(void)
> {
> return syscall(SYS_gettid);
> }
> @@ -72,7 +72,7 @@ test_assert(bool exp, const char *exp_str,
> fprintf(stderr, "==== Test Assertion Failure ====\n"
> " %s:%u: %s\n"
> " pid=%d tid=%d - %s\n",
> - file, line, exp_str, getpid(), gettid(),
> + file, line, exp_str, getpid(), _gettid(),
> strerror(errno));
> test_dump_stack();
> if (fmt) {
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2019-11-13 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 12:51 Vitaly Kuznetsov
2019-11-13 14:48 ` Paolo Bonzini [this message]
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=f439dee6-012a-d9aa-5f16-cbd911d6d55d@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@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
all inboxes | Powered by JetHome®