Bug 176809
Summary: | journal_start crashed when doing long time test | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | liubin <liub> |
Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jbaron, rwheeler |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | Unable to handle kernel NULL pointer dereference at virtual address 000000b0 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-16 18:47:13 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: |
Description
liubin
2006-01-03 06:34:52 UTC
000006bf <journal_start>: 6bf: 57 push %edi 6c0: bf 00 f0 ff ff mov $0xfffff000,%edi 6c5: 56 push %esi 6c6: 89 c6 mov %eax,%esi 6c8: 53 push %ebx 6c9: 21 e7 and %esp,%edi 6cb: 8b 07 mov (%edi),%eax 6cd: 85 f6 test %esi,%esi if (!journal) 6cf: 8b 98 a8 05 00 00 mov 0x5a8(%eax),%ebx journal_current_handle() ?? 6d5: b8 e2 ff ff ff mov $0xffffffe2,%eax -EROFS (-30) 6da: 74 7d je 759 <journal_start+0x9a> if no journal return -EROFS 6dc: 85 db test %ebx,%ebx if (handle) BUT handle/%ebx is 0xb0?! 6de: 74 34 je 714 <journal_start+0x55> if no handle jump to new_handle 6e0: 8b 03 mov (%ebx),%eax <-- died here (try to use %ebx/handle) Unable to handle kernel NULL pointer dereference at virtual address 000000b0 kernel: eax: ffffffe2 ebx: 000000b0 ecx: df57a400 edx: 0000005d kernel: esi: df762800 edi: c5ed5000 ebp: 000081b6 esp: c5ed5edc kernel: ds: 007b es: 007b ss: 0068 it looks like current->journal_info is corrupt, which could be due to any number of reasons, all impossible to tell from the info here, I'm afraid. Has this been seen since? Please reopen if you still have this issue. |