Bug 480666

We are hitting this problem in RHEL4 here
https://bugzilla.redhat.com/show_bug.cgi?id=455696

so I cloned the 5.4 bz to 4.7.

Oh yeah, I ported the upstream patch to RHEL4 here
https://bugzilla.redhat.com/attachment.cgi?id=329133

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Mike - I'm assuming this is a post-Beta candidate for 4.8?

Rob is working on it. We are having troubles with the ported patch not working as expected.

I think Tom really wants this to go in before a beta, so that is gets a lot of testing, and I agree that it needs lots of testing to make sure it will not cause a regression. So I guess if we do not make beta then it is 4.9???? Am I in sync with what everyone else was thinking?

the problems I was seeing with the rhel4.8 ported patch were due to a bug in the test code I was using.  Once the test code was fixed, the patch worked as expected.

Committed in 81.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/

~~ Attention Partners!  ~~
RHEL 4.8 Partner Alpha has been released on partners.redhat.com. There should be a fix present in the Beta, which addresses this URGENT priority bug. If you haven't had a chance yet to test this bug, please do so at your earliest convenience, to ensure that only the highest possible quality bits are shipped in the upcoming public Beta drop.

If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. Further questions can be directed to your Red Hat Partner Manager.

Thanks, more information about Beta testing to come.
 - Red Hat QE Partner Management

~~ Attention Partners!  ~~
RHEL 4.8 Partner Alpha has been released on partners.redhat.com. There should
be a fix present in the Beta, which addresses this bug. If you have already completed testing your other URGENT priority bugs, and you still haven't had a chance yet to test this bug, please do so at your earliest convenience, to ensure that only the highest possible quality bits are shipped in the upcoming public Beta drop.

If you encounter any issues, please set the bug back to the ASSIGNED state and
describe the issues you encountered. Further questions can be directed to your
Red Hat Partner Manager.

Thanks, more information about Beta testing to come.
 - Red Hat QE Partner Management

~~ Attention Partners!  ~~
RHEL 4.8Beta has been released on partners.redhat.com. There should
be a fix present, which addresses this bug. Please test and report back results on this OtherQA Partner bug at your earliest convenience.

If you encounter any issues, please set the bug back to the ASSIGNED state and
describe any issues you encountered. If you have found a NEW bug, clone this bug and describe the issues you've encountered. Further questions can be directed to your Red Hat Partner Manager.

If you have VERIFIED the bug fix. Please select your PartnerID from the Verified field above. Please leave a comment with your test results details. Include which arches tested, package version and any applicable logs.

 - Red Hat QE Partner Management

Emulex, please verify this bug has been resolved in the recently release RHEL4.8 Beta and update test results here.

Verified.  RHEL 4.8 beta's kernel (2.6.9-82.EL) does not get data corruption in the NO_SENSE test case where earlier kernels (e.g. 2.6.9-67.EL) did see data corruption.

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/RHSA-2009-1024.html