Bug 1871382 - glibc: Improve stdio implementation.
Summary: glibc: Improve stdio implementation.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: glibc team
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-23 01:17 UTC by Carlos O'Donell
Modified: 2023-07-18 14:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-02 16:27:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Sourceware 14231 0 P2 RESOLVED stdio-common tests memory requirements 2020-10-14 13:20:35 UTC
Sourceware 25691 0 P2 RESOLVED printf: memory leak when printing long multibyte strings 2020-10-14 13:20:36 UTC
Sourceware 26211 0 P2 RESOLVED printf integer overflow calculating allocation size 2020-10-14 13:20:36 UTC
Sourceware 26214 0 P2 RESOLVED printf_fp double free 2020-10-14 13:20:37 UTC
Sourceware 26215 0 P2 RESOLVED printf_fp memory leak 2020-10-14 13:20:37 UTC

Description Carlos O'Donell 2020-08-23 01:17:29 UTC 
Backport the following fixes to improve the stdio implementation:

3cc4a8367c23582b7db14cf4e150e4068b7fd461
stdio: Remove memory leak from multibyte convertion [BZ#25691]

910a835dc96c1f518ac2a6179fc622ba81ffb159
stdio: Add tests for printf multibyte convertion leak [BZ#25691]

6caddd34bd7ffb5ac4f36c8e036eee100c2cc535
Remove most vfprintf width/precision-dependent allocations (bug 14231, bug 26211).

ede56038e50235cd1ca7de3602c9491d3b84b49b
Fix double free in __printf_fp_l (bug 26214).

90663e9c814a919fa1fb41a878c06ef2fae58ed2
Fix memory leak in __printf_fp_l (bug 26215).
Comment 6 RHEL Program Management 2022-02-23 07:27:20 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 7 Carlos O'Donell 2022-02-23 14:05:35 UTC 
Reopening for planning purposes.
Note You need to log in before you can comment on or make changes to this bug.