* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
@ 2020-10-29 8:42 ` nsz at gcc dot gnu.org
2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
` (11 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: nsz at gcc dot gnu.org @ 2020-10-29 8:42 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
Szabolcs Nagy <nsz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at sourceware dot org |nsz at gcc dot gnu.org
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
2020-10-29 8:42 ` [Bug dynamic-link/26798] " nsz at gcc dot gnu.org
@ 2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
` (10 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-02 9:40 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Szabolcs Nagy <nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=558251bd8785760ad40fcbfeaaee5d27fa5b0fe4
commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
2020-10-29 8:42 ` [Bug dynamic-link/26798] " nsz at gcc dot gnu.org
2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
@ 2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
2020-11-02 10:45 ` fweimer at redhat dot com
` (9 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-02 9:40 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Szabolcs Nagy <nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e156dabc766d6f6f99ce9402999eae380a3ec1f2
commit e156dabc766d6f6f99ce9402999eae380a3ec1f2
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Mon Oct 26 15:48:01 2020 +0000
aarch64: Add variant PCS lazy binding test [BZ #26798]
This test fails without bug 26798 fixed because some integer registers
likely get clobbered by lazy binding and variant PCS only allows x16
and x17 to be clobbered at call time.
The test requires binutils 2.32.1 or newer for handling variant PCS
symbols. SVE registers are not covered by this test, to avoid the
complexity of handling multiple compile- and runtime feature support
cases.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (2 preceding siblings ...)
2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
@ 2020-11-02 10:45 ` fweimer at redhat dot com
2020-11-02 13:31 ` nsz at gcc dot gnu.org
` (8 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: fweimer at redhat dot com @ 2020-11-02 10:45 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
See Also| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=1893662
Flags| |security-
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (3 preceding siblings ...)
2020-11-02 10:45 ` fweimer at redhat dot com
@ 2020-11-02 13:31 ` nsz at gcc dot gnu.org
2020-11-02 13:33 ` nsz at gcc dot gnu.org
` (7 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: nsz at gcc dot gnu.org @ 2020-11-02 13:31 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
Szabolcs Nagy <nsz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.33
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (4 preceding siblings ...)
2020-11-02 13:31 ` nsz at gcc dot gnu.org
@ 2020-11-02 13:33 ` nsz at gcc dot gnu.org
2020-11-04 12:37 ` cvs-commit at gcc dot gnu.org
` (6 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: nsz at gcc dot gnu.org @ 2020-11-02 13:33 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
Szabolcs Nagy <nsz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Szabolcs Nagy <nsz at gcc dot gnu.org> ---
fixed on master.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (5 preceding siblings ...)
2020-11-02 13:33 ` nsz at gcc dot gnu.org
@ 2020-11-04 12:37 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:39 ` cvs-commit at gcc dot gnu.org
` (5 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:37 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.32/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=70ee5e8b573f76745760dd6b75f705590fc1923a
commit 70ee5e8b573f76745760dd6b75f705590fc1923a
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (6 preceding siblings ...)
2020-11-04 12:37 ` cvs-commit at gcc dot gnu.org
@ 2020-11-04 12:39 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:40 ` cvs-commit at gcc dot gnu.org
` (4 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:39 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.31/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8dc76056654f8013a54678461fb023e988a17256
commit 8dc76056654f8013a54678461fb023e988a17256
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (7 preceding siblings ...)
2020-11-04 12:39 ` cvs-commit at gcc dot gnu.org
@ 2020-11-04 12:40 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:42 ` cvs-commit at gcc dot gnu.org
` (3 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:40 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.30/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=61e8ae9b660d98d3a139d3dd617dea16de798f88
commit 61e8ae9b660d98d3a139d3dd617dea16de798f88
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (8 preceding siblings ...)
2020-11-04 12:40 ` cvs-commit at gcc dot gnu.org
@ 2020-11-04 12:42 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
` (2 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:42 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.29/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a3c78954ee0009e558b7e6b9eb05208814099e21
commit a3c78954ee0009e558b7e6b9eb05208814099e21
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (9 preceding siblings ...)
2020-11-04 12:42 ` cvs-commit at gcc dot gnu.org
@ 2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:45 ` cvs-commit at gcc dot gnu.org
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:44 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.28/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d81114e0aaedc30d82956d3a21ae6777b3fbba3c
commit d81114e0aaedc30d82956d3a21ae6777b3fbba3c
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (10 preceding siblings ...)
2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
@ 2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:45 ` cvs-commit at gcc dot gnu.org
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:44 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.27/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=dc7f51bda99fa8eceb7f9049c0a9827064ff7e85
commit dc7f51bda99fa8eceb7f9049c0a9827064ff7e85
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
2020-10-28 9:23 [Bug dynamic-link/26798] New: aarch64: variant PCS symbols may be incorrectly lazy bound nsz at gcc dot gnu.org
` (11 preceding siblings ...)
2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
@ 2020-11-04 12:45 ` cvs-commit at gcc dot gnu.org
12 siblings, 0 replies; 14+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-04 12:45 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.26/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=268df5a91054fcb4284e8504afd086a769ec4c40
commit 268df5a91054fcb4284e8504afd086a769ec4c40
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread