Bug 2215368 - glibc: strerror must not return NULL
Summary: glibc: strerror must not return NULL
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: glibc
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Arjun Shankar
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-15 17:58 UTC by Florian Weimer
Modified: 2023-07-23 18:24 UTC (History)
7 users (show)

Fixed In Version: glibc-2.34-69.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-160011 0 None None None 2023-06-15 17:58:59 UTC

Description Florian Weimer 2023-06-15 17:58:18 UTC 
We need to backport this commit to avoid a regression from glibc 2.28:

commit 1d44530a5be2442e064baa48139adc9fdfb1fc6b
Author: Florian Weimer <fweimer>
Date:   Thu Jun 15 12:08:22 2023 +0200

    string: strerror must not return NULL (bug 30555)
    
    For strerror, this fixes commit 28aff047818eb1726394296d27b ("string:
    Implement strerror in terms of strerror_l").  This commit avoids
    returning NULL for strerror_l as well, although POSIX allows this
    behavior for strerror_l.
    
    Reviewed-by: Arjun Shankar <arjun>
Note You need to log in before you can comment on or make changes to this bug.