Bug 173364
| Summary: | Kernel panic - not syncing: bad locking | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> | ||||||
| Component: | kernel | Assignee: | Steve Dickson <steved> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rawhide | CC: | davej, rvokal, wtogami | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2006-03-06 17:39:02 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
Bill Nottingham
2005-11-16 16:45:43 UTC
OK, copying by hand:
Call Trace:<ffffffff8013a7b1>{panic+133} <ffffffff8014dfad>{kernel_text_address+28}
<fffffff80110302>{show_trace+505} <ffffffff8011036e>{dump_stack+14}
<ffffffff8021df11>{spin_bug+222} <ffffffff8021e1fa>{_raw_spin_lock+58}
<ffffffff884199b2>{:nfs:nfs_zap_caches+40}
<ffffffff8841a1ec>{:nfs:nfs_update_inode+1131}
<ffffffff8841a2a2>{:nfs:nfs_post_op_update_inode+68}
<ffffffff8842303c>{:nfs:nfs3_proc_remove+197}
<ffffffff8019c9ce>{__link_path_walk+378}
<ffffffff801efa7e>{avc_has_perm+70} <ffffffff803696e4>{lock_kernel+45}
<ffffffff88417b39>{:nfs:nfs_unlink+349} <ffffffff819e4a2>{vfs_unlink+452}
<ffffffff8019ed58>{sys_unlink+214} <ffffffff801119ea>{syscall_trace_enter+217}
<ffffffff80111a27>{syscall_trace_leave+55} <ffffffff8010ebdc>{tracesys+113}
<ffffffff8010ec3c>{tracesys+209}
Version is 2.6.14-1.1665_FC5 Still happens with 1682. Created attachment 121206 [details]
proposed patch
Created attachment 121221 [details]
Upstream patch
Here is the upstream patch for this problem....
applied to CVS, will be in all post 1698 kernels. Thanks Steve. This doesn't panic, but it does produce the following errors: nfs_update_inode: inode 31385370 mode changed, 0042775 to 0002775 nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0xf85f85) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1e5f27) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) nfs_update_inode: inode 31385370 mode changed, 0042775 to 0002775 nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) nfs_update_inode: inode 31385370 mode changed, 0042775 to 0002775 nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1e5f27) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) nfs_update_inode: inode 31385370 mode changed, 0042775 to 0002775 nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1e5f27) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x0) nfs_update_inode: inode 31385370 mode changed, 0042775 to 0002775 nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x100000000000000) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x100000000000000) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x846922) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x0) nfs_update_inode: inode number mismatch expected (0:16/0x1dee71a), got (0:16/0x1dee719) still a problem ? Still have the inode number mismatch messages (as of 1725), yes. Well there were two problems here... on was the panic and the second was the "nfs_update_inode: inode number mismatch" We've fixed the first one and the second one is more of a warning that anything... its saying that the cached inode number does not match the the inode number the server just gave out. which is probably is a more of server problem than a client one.... Does the inode message happen alot? Happens consistently with this usage case, doesn't seem to happen at all otherwise. *shrug* Lets close the bug and Bill open another one about the constant warning messages |