diff options
| author | Davide Cavalca <davide@cavalca.name> | 2025-07-31 17:32:58 +0200 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2025-07-31 19:11:08 +0200 |
| commit | d9a348d0927c7a1aec5caf3df3fcd36956b3eb23 (patch) | |
| tree | eeeff5d9c349faceda6f1e4d1441230582b0c00f /sysdeps/arm/armv7/multiarch/memcpy_neon.S | |
| parent | 258126bc0b77d7f9ae7d0b2737ec66e186c1e0ef (diff) | |
| download | glibc-master.zip glibc-master.tar.gz glibc-master.tar.bz2 | |
The __abort_fork_reset_child (introduced in
d40ac01cbbc66e6d9dbd8e3485605c63b2178251) call resets the lock after the
fork. This causes a DRD regression in valgrind
(https://bugs.kde.org/show_bug.cgi?id=503668), as it's effectively a
double initialization, despite it being actually ok in this case. As
suggested in https://sourceware.org/bugzilla/show_bug.cgi?id=32994#c2
we replace it here with a memcpy of another initialized lock instead,
which makes valgrind happy.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
Diffstat (limited to 'sysdeps/arm/armv7/multiarch/memcpy_neon.S')
0 files changed, 0 insertions, 0 deletions