From: Sean Christopherson <seanjc@google.com>
To: Liam Merwick <liam.merwick@oracle.com>
Cc: kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
pbonzini@redhat.com, gshan@redhat.com, oliver.upton@linux.dev,
andrew.jones@linux.dev
Subject: Re: [PATCH] KVM: selftests: Make rseq compatible with versions prior to glibc-2.30
Date: Wed, 7 Sep 2022 16:00:04 +0000 [thread overview]
Message-ID: <YxjABH3Fw7W+NE8J@google.com> (raw)
In-Reply-To: <20220907155510.968666-1-liam.merwick@oracle.com>
On Wed, Sep 07, 2022, Liam Merwick wrote:
> The fix for commit e923b0537d28 ("KVM: selftests: Fix target thread to be migrated in rseq_test")
> added a call to gettid() which was only added to glibc-2.30 and fails to
> compile with older glibc versions.
>
> rseq_test.c: In function 'main':
> rseq_test.c:230:33: warning: implicit declaration of function 'gettid'; did you mean 'getgid'? [-Wimplicit-function-declaration]
> (void *)(unsigned long)gettid());
> ^~~~~~
> getgid
>
> Switch the call to syscall(SYS_gettid) which was the original advice in the
> gettid(2) NOTES section and which works with both new and older glibc versions.
>
> Fixes: e923b0537d28 ("KVM: selftests: Fix target thread to be migrated in rseq_test")
> Cc: stable@vger.kernel.org # v5.15
> Signed-off-by: Liam Merwick <liam.merwick@oracle.com>
> ---
>
> Verified with glibc-2.28 and glibc-2.34 and ensured test case from e923b0537d28 still passes.
>
> tools/testing/selftests/kvm/rseq_test.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/rseq_test.c b/tools/testing/selftests/kvm/rseq_test.c
> index fac248a43666..6f88da7e60be 100644
> --- a/tools/testing/selftests/kvm/rseq_test.c
> +++ b/tools/testing/selftests/kvm/rseq_test.c
> @@ -227,7 +227,7 @@ int main(int argc, char *argv[])
> ucall_init(vm, NULL);
>
> pthread_create(&migration_thread, NULL, migration_worker,
> - (void *)(unsigned long)gettid());
> + (void *)(unsigned long)syscall(SYS_gettid));
This exact fix was already posted[*], but we rat-holed a bit on coming up with an
elegant solution and the patch never got applied. I'll poke that thread to see if
Paolo wants to take it for 6.0.
[*] https://lore.kernel.org/all/20220802071240.84626-1-cloudliang@tencent.com
prev parent reply other threads:[~2022-09-07 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 15:55 [PATCH] KVM: selftests: Make rseq compatible with versions prior to glibc-2.30 Liam Merwick
2022-09-07 16:00 ` Sean Christopherson [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=YxjABH3Fw7W+NE8J@google.com \
--to=seanjc@google.com \
--cc=andrew.jones@linux.dev \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liam.merwick@oracle.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@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