RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 598782 [details]
rsync.spec.diff

Description of problem:
The Red Hat rsync-3.0.6 RPM does not have the posix_fadvise patch applied.

This patch is not required for correct operation of rsync but it does improve system performance with respect to cached file blocks in memory.  More information is available at http://insights.oetiker.ch/linux/fadvise/

It would be a 'nice to have' if this patch were applied in the official Red Hat RPM's.

Version-Release number of selected component (if applicable):
Red Hat rsync-3.0.6 RPM and below. 
Probably all Red Hat builds of rsync RPMs.

How reproducible:
n/a

Steps to Reproduce:
n/a
  
Actual results:
n/a

Expected results:
n/a

Additional info:
The patch is supplied with the pristine rsync sources in patches/drop-cache.diff

I obtained the SRPM (rsync-3.0.6-4.el5_7.1.src.rpm) and modified rsync.spec to apply this patch (see attached rsync.spec.diff for changes). This broke application of rsync-3.0.7-ftrunc-sparse-files.patch, so I made appropriate modifications (see attached rsync-3.0.7-ftrunc-sparse-files.patch.diff for changes).

Created attachment 598783 [details]
rsync-3.0.7-ftrunc-sparse-files.patch.diff

This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be moved to Red Hat Enterprise Linux 6. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.

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