This bug has been copied from bug #253356 and has been proposed to be backported to 5.1 z-stream (EUS).
The backport patch for bug# 253356 has been posted and ACKed. Do I need to post again for this bz? Or I just need to change the status to POST to reflect the right status?
No, you should not do anything here. :) Thanks for your job.
A patch for this issue has been included in build 2.6.18-53.1.2
I just ran the test script on hp-merlion-01.rhts.boston.redhat.com using a RHEL 4 i386 box for the nfs server. With the -53 kernel I was able to reproduce the problem. I've since tried 3 runs with the 53.1.4 kernel and the system seems to be holding up well, no softlockups or anything else suspicious in the logs.
No errors or softlockups after a fourth run. Suspect we might have another bug here somewhere that either happens very rarely or the softlockup has some other cause. I'm going to go ahead and set this one to verified.
Re comment#9: what is you test case? Sounds like this is another problem. Because the bug seems to just affect the process whose code segment is on nfs server. The patch is to sync cache .., So I don't see how it could cause system hang. But I will run some testing for sure.
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 the 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-2007-0993.html