public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ludwig.rydberg at gaisler dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31068] New: sysdeps: sparc: invalid data access in memset due to regression
Date: Wed, 15 Nov 2023 09:32:23 +0000 [thread overview]
Message-ID: <bug-31068-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31068
Bug ID: 31068
Summary: sysdeps: sparc: invalid data access in memset due to
regression
Product: glibc
Version: 2.36
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: ludwig.rydberg at gaisler dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Description:
When testing the glibc-master (2023-11-13) on sparc32 (leon) a memset
regression was observed.
The issue was introduced by commit a61933fe27df ("sparc: Remove bzero
optimization").
How to reproduce:
It can be reproduced running the "string/test-memset" test on sparc32.
Fail rate: 100%
Test output:
string/test-memset.test-result:
FAIL: string/test-memset
original exit status 1
string/test-memset.out:
Didn't expect signal from child: got `Segmentation fault'
Root cause:
The reason for the issue was that when moving the bzero routine to the end of
the memset, the branch jump in the end made a jump back to wrong label causing
the invalid data access.
A fix has been implemented and will be submitted.
--
glibc version: master d1dcb565a1fb (2023-11-13)
- The issue was first observed in glibc-2.36.
gcc version 10.2.0 (LEON Linux 5.10 Toolchain 1.4-87-gcd8128e)
- sparc-gaisler-linux5.10
GNU ld (GNU Binutils) 2.34
glibc configure options:
--prefix=/usr --enable-bind-now --host=sparc-gaisler-linux5.10
--with-headers=$USER/git/linux-toolchain/build-gcc-linux64//opt/sparc-gaisler-linux5.10/sysroot/usr/include
--with-binutils=$USER/git/linux-toolchain/build-gcc-linux64/binutils/binutils
--disable-default-pie libc_cv_forced_unwind=yes libc_cv_ssp=no
Target: Linux buildroot 5.10.175-leon1.4
Host: Ubuntu 22.04 6.2.0-36-generic
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-11-15 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 9:32 ludwig.rydberg at gaisler dot com [this message]
2023-11-15 9:34 ` [Bug libc/31068] " sam at gentoo dot org
2023-11-16 14:11 ` adhemerval.zanella at linaro dot org
2024-02-01 20:06 ` pinskia at gcc dot gnu.org
2024-02-01 20:14 ` glaubitz at physik dot fu-berlin.de
2024-02-01 20:51 ` adhemerval.zanella at linaro dot org
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=bug-31068-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).