Bug 187523

Summary: kernel panic when using smbfs and timeout/lost connection occurs
Product: Red Hat Enterprise Linux 4 Reporter: Robert Hare <rhare>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0CC: jbaron, staubach, steved
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-15 11:35:46 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:
Attachments:
Description Flags
messages file showing errors and panic none

Description Robert Hare 2006-03-31 16:57:40 UTC 
Kernel panic when accessing SMBFS (windows server) mounted on linux box
RHEL4 all patches applied


How reproducible:
Frequently on large windows filesystem.

Steps to Reproduce:
1. Mount filesystem
2. Perform large action like du -s on filesystem
3. Panic
  
Actual results:
Panic

Expected results:
No panic

Additional info:
Seems to be related to timeouts or lost connections.
Comment 1 Robert Hare 2006-03-31 16:57:40 UTC 
Created attachment 127134 [details]
messages file showing errors and panic
Comment 2 Robert Hare 2006-04-28 17:24:32 UTC 
I have now duplicated the problem on another RH EL 4 box, so the problem is not 
specific to one machine.
Comment 3 Jeff Layton 2007-07-19 14:31:42 UTC 
A couple of different smbfs memory corruption patches are being committed for
4.6.  It's possible that this problem is also fixed there. If you're able to
reproduce this someplace non-critical, then testing the kernels on my people
page would be helpful:

http://people.redhat.com/jlayton
Comment 4 Jeff Layton 2008-01-15 11:35:46 UTC 
No response in several months. Closing bug with resolution of INSUFFICIENT_DATA,
please reopen if you're still having this issue (though the best solution is
probably to go ahead and move to CIFS).