Bug 661982

Summary:	memmove/wmemmove/wmemset __restrict fixes
Product:	Red Hat Enterprise Linux 6	Reporter:	Jakub Jelinek <jakub>
Component:	glibc	Assignee:	Andreas Schwab <schwab>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.1	CC:	fweimer, mfranc, pmuller
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glibc-2.12-1.17	Doc Type:	Bug Fix
Doc Text:	The memmove, wmemmove and wmemset operations contained incorrect "__restrict" qualifiers, even though their arguments could overlap. This issue has now been corrected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-19 13:16:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jakub Jelinek 2010-12-10 08:58:38 UTC

As reported in http://gcc.gnu.org/PR46863, memmove (and apparently wmemmove too) have incorrect __restrict qualifiers, eventhough their arguments may overlap.

memmove has been fixed in git already (though, the git commit apparently also includes an unrelated hunk in some *.S file), wmemmove/wmemset fix has just been posted.

This should be backported for RHEL 6.1.

Comment 3 Laura Bailey 2011-05-16 01:53:33 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The memmove, wmemmove and wmemset operations contained incorrect "__restrict" qualifiers, even though their arguments could overlap. This issue has now been corrected.

Comment 4 errata-xmlrpc 2011-05-19 13:16:19 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0584.html