Bug 663353

Summary: System crashes at .nfs_flush_incompatible [rhel-5.5.z]
Product: Red Hat Enterprise Linux 5 Reporter: RHEL Program Management <pm-rhel>
Component: kernelAssignee: Jiri Pirko <jpirko>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: urgent    
Version: 5.5CC: bfields, dhoward, eguan, jkachuck, jlayton, jpirko, jwest, pm-eus, rkhan, rwheeler, steved, tao, trond.myklebust, yanwang
Target Milestone: rcKeywords: OtherQA, Regression, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.18-194.31.1.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-04 16:54:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 656492    
Bug Blocks:    

Description RHEL Program Management 2010-12-15 14:13:39 UTC
This bug has been copied from bug #656492 and has been proposed
to be backported to 5.5 z-stream (EUS).

Comment 3 Jiri Pirko 2010-12-16 15:06:21 UTC
in kernel-2.6.18-194.31.1.el5

linux-2.6-fs-nfs-remove-problematic-calls-to-nfs_clear_request.patch
linux-2.6-fs-nfs-handle-alloc-failures-in-nfs_create_request.patch
linux-2.6-fs-nfs-clean-up-nfs_create_request.patch

Comment 5 Eryu Guan 2010-12-23 07:40:01 UTC
The fix has been verified by IBM, bug 656492 comment 76. I ran connectathon tests no issue found, confirmed patches are applied in kernel 2.6.18-194.32.1.el5 correctly. Set SanityOnly

joblinks
https://beaker.engineering.redhat.com/jobs/41668
https://beaker.engineering.redhat.com/jobs/41669
https://beaker.engineering.redhat.com/jobs/41670
https://beaker.engineering.redhat.com/jobs/41671
https://beaker.engineering.redhat.com/jobs/41672

Comment 7 errata-xmlrpc 2011-01-04 16:54:36 UTC
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-2011-0004.html