Bug 2091549
Summary: | glibc: Incorrect results of POWER9-optimized strncpy [rhel-9.1.0] | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Florian Weimer <fweimer> | |
Component: | glibc | Assignee: | glibc team <glibc-bugzilla> | |
Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> | |
Severity: | medium | Docs Contact: | mtimar | |
Priority: | unspecified | |||
Version: | 9.1 | CC: | ashankar, codonell, dj, fweimer, mcoufal, mnewsome, mscastanho, mtimar, pfrankli, sipoyare, tulioqm | |
Target Milestone: | rc | Keywords: | Bugfix, Triaged, ZStream | |
Target Release: | 9.1 | |||
Hardware: | ppc64le | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | glibc-2.34-37.el9 | Doc Type: | Bug Fix | |
Doc Text: |
.POWER9-optimized strncpy function no longer gives incorrect results
Previously, the POWER9 strncpy function did not use the correct register as the source of the NUL bytes for padding. Consequently, the output buffer contained uninitialized register content instead of the NUL padding. With this update, the strncpy function has been fixed, and the end of the output buffer is now correctly padded with NUL bytes.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2091553 2095450 (view as bug list) | Environment: | ||
Last Closed: | 2022-11-15 11:11:50 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 2091541 | |||
Bug Blocks: | 2091553, 2095450 |
Description
Florian Weimer
2022-05-30 09:59:29 UTC
The fix has been applied upstream for glibc 2.36 and has been backported to glibc >= 2.33. Commit for glibc 2.36: https://sourceware.org/git/?p=glibc.git;a=commit;h=0218463dd8265ed937622f88ac68c7d984fe0cfc Commit for glibc 2.34: https://sourceware.org/git/?p=glibc.git;a=commit;h=4c92a1041257c0155c6aa7a182fe5f78e477b0e6 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glibc bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8272 |