Bug 143918
Summary: | kernel panic | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | NiCK <song> | ||||
Component: | kernel | Assignee: | Alexander Viro <aviro> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | anderson, lwoodman, petrides, riel, shillman | ||||
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: | 2007-10-19 19:10:14 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
NiCK
2005-01-01 11:03:12 UTC
What was going on that caused this? What is the hardware of machine in question, and is the problem reproducible? Created attachment 109307 [details]
sysreport result
hi,Suzanne Hillman. Comment #2 is sysreport result. The problem occurs once a day or 2 days or 3 days. This crash appears to be caused by a corrupt fops struct in dentry_open(). dentry_open()------------------------ f->f_op = fops_get(inode->i_fop); ... if (f->f_op && f->f_op->open) { error = f->f_op->open(inode,f); ... ------------------------------------- Can you reproduce this with the RHEL3-U4 kernel? We did fix corruption problems in that kernel. 7273752f => "/vsr". Not something one would expect to find in page table... Care to post other oopsen of the same sort? This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |