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.

Description of problem:
hitting this bug:
https://svn.boost.org/trac/boost/ticket/3352 
CRC not correctly computed on x64 during decompression of gzip archive

Version-Release number of selected component (if applicable):
boost-1.41.0-11.el6.x86_64


How reproducible:
always

Steps to Reproduce:
install:
boost-devel-1.41.0-11.el6.x86_64
boost-iostreams-1.41.0-11.el6.x86_64
boost-system-1.41.0-11.el6.x86_64

Compile the attached C++ program:
Put both test.cpp and test.gz in the current directory.
make test CXXFLAGS="-O3 -m64" LDFLAGS="-lboost_iostreams-mt -lboost_system-mt"

Verify the test.gz attached is in the same directory as the new executable.
zcat test.gz | wc -l
41320

Here's the expected output, which I get when test.cpp is compiled on RHEL6 Beta 1 (boost-1.39.0-8.1.el6.x86_64):
./test
41320

Note that it matches the output of the previous command.

Here's the result when this is compiled on current RHEL6:
./test
Error reading input: 41313
  
Actual results:
Error reading input: 41313


Expected results:
41320

Additional info:

Created attachment 500843 [details]
test C program

Created attachment 500845 [details]
test gzip archive

Created attachment 506193 [details]
Candidate fix

I believe that this should fix the problem.  I'll go ahead and verify whether it actually does.

It does.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

This seems to have been fixed already in 1.41.0-11.1 - presumably this bug should be closed?

This is kept open for process-related reasons.

Since this is a parent bug of an issue that has already been released via Z-Stream (e.g. rhel-6.3.z), this bug is going to be CLOSED as CURRENTRELEASE.

Z-stream? What's that?