Bug 1291714

Summary:	grep 2.20 lost the --mmap option
Product:	Red Hat Enterprise Linux 6	Reporter:	Sven Hoexter <sven>
Component:	grep	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	jkejda, ovasik, thozza
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-05 14:37:55 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:

Description Sven Hoexter 2015-12-15 13:40:42 UTC

Hi,
with the switch from grep 2.6 to 2.20 grep lost the --mmap option.
I don't want to seriously argue about adding it back just for backwards
compatibility, I just could not spot that one in the release notes.

We fixed the one point where it broke something for good. :)

Comment 2 Jaroslav Škarvada 2015-12-15 14:51:06 UTC

AFAIK the --mmap option has been deprecated since grep-2.5.4. The option was initially removed by an mistake by grep upstream, but later (IIRC in grep-2.7) the option was added back for compatibility purposes, but it do nothing. We backported this to grep-2.6.3, so the --mmap didn't cause error, but did nothing. This patch was probably mistakenly dropped during the rebase. I think it should be added back not to cause regression.

Comment 4 Sven Hoexter 2015-12-16 08:37:07 UTC

From my point of view it's enough to just add this information to the release notes. I'd guess for most people the "damage" is already done, and they might have already fixed those occurrences like we did.

Comment 10 Tomáš Hozza 2017-09-05 14:37:55 UTC

Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle

This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com