From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] powerpc64le/power9: guard power9 strcmp against rtld usage [BZ# 25905]
Date: Mon, 4 May 2020 09:26:12 -0300 [thread overview]
Message-ID: <27007d15-933d-8d13-161f-cab2b26b37f2@linaro.org> (raw)
In-Reply-To: <20200501203219.8738-1-murphyp@linux.vnet.ibm.com>
On 01/05/2020 17:32, Paul E. Murphy via Libc-alpha wrote:
> strcmp is used while resolving PLT references. Vector registers
> should not be used during this. The P9 strcmp makes heavy use of
> vector registers, so it should be avoided in rtld.
>
> This prevents quiet vector register corruption when glibc is configured
> with --disable-multi-arch and --with-cpu=power9. This can be seen with
> test-float64x-compat_totalordermag during the first call into
> totalordermagf64x@GLIBC_2.27.
>
> Add a guard to fallback to the power8 implementation when building
> power9 strcmp for libraries other than libc.
The more usual way and it has the advantages of decouple the generic
implementation and make it more explicit is to add a new rtld-strcmp.S
file:
$ cat sysdeps/powerpc/powerpc64/le/power9/rtld-strcmp.S
#include <sysdeps/powerpc/powerpc64/power8/strcmp.S>
> ---
> sysdeps/powerpc/powerpc64/le/power9/strcmp.S | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/sysdeps/powerpc/powerpc64/le/power9/strcmp.S b/sysdeps/powerpc/powerpc64/le/power9/strcmp.S
> index 412a13599d..b29ea7c020 100644
> --- a/sysdeps/powerpc/powerpc64/le/power9/strcmp.S
> +++ b/sysdeps/powerpc/powerpc64/le/power9/strcmp.S
> @@ -17,6 +17,11 @@
> <https://www.gnu.org/licenses/>. */
> #include <sysdep.h>
>
> +#if !IS_IN(libc)
> +/* Fallback to P8 which does not use vector regs for rtld. */
> +#include <sysdeps/powerpc/powerpc64/power8/strcmp.S>
> +#else
> +
> #ifndef STRCMP
> # define STRCMP strcmp
> #endif
> @@ -262,3 +267,5 @@ L(pagecross_nullfound):
> b L(pagecross_retdiff)
> END (STRCMP)
> libc_hidden_builtin_def (strcmp)
> +
> +#endif
>
next prev parent reply other threads:[~2020-05-04 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:32 Paul E. Murphy
2020-05-04 12:26 ` Adhemerval Zanella [this message]
2020-05-04 15:25 ` [PATCHv2] " Paul E. Murphy
2020-05-04 16:36 ` Adhemerval Zanella
2020-05-04 18:02 ` Paul E Murphy
2020-05-04 18:26 ` Adhemerval Zanella
2020-05-04 21:16 ` Paul E Murphy
2020-05-05 21:01 ` Adhemerval Zanella
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=27007d15-933d-8d13-161f-cab2b26b37f2@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).