Bug 156635
Summary: | gfs i/o regression on rhel3-u5 | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Corey Marthaler <cmarthal> |
Component: | gfs | Assignee: | Ben Marzinski <bmarzins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | GFS Bugs <gfs-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
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: | 2010-10-29 21:49:35 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
Corey Marthaler
2005-05-02 19:23:47 UTC
ia64 stack: Pid: 6666, comm: doio EIP is at kfree [kernel] 0xe0 (2.4.21-32.EL) psr : 0000101008022018 ifs : 800000000000038a ip : [<e0000000044e55a0>] Not tainted unat: 0000000000000000 pfs : 000000000000038a rsc : 0000000000000003 rnat: 0000000000000000 bsps: 0000000000000000 pr : fffefff5a5559555 ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70033f b0 : e0000000044e5530 b6 : e0000000044e54c0 b7 : e000000004415240 f6 : 1003e0000000000000010 f7 : 0fff3ac25500000000000 f8 : 1003e0000000000007ff0 f9 : 1003e00000000000007ff r1 : e000000004cbbd00 r2 : 00000000000000b0 r3 : 0000000000000000 r8 : 0000000000000000 r9 : e000000035a6803c r10 : a0000000006f4990 r11 : e0000000015fde30 r12 : e000000035a6fc30 r13 : e000000035a68000 r14 : e000000004b8bb10 r15 : 0000000000000000 r16 : 000000000005de3d r17 : e00000000101fa60 r18 : 000000000006b4d8 r19 : e000000004d33848 r20 : e000000004415240 r21 : e0000000049913b8 r22 : e000000004b8bb40 r23 : e000000004b8bb10 r24 : a0000000006f4998 r25 : e0000000042ef838 r26 : e0000000042ef830 r27 : e000000035a69810 r28 : fffefff5a555a555 r29 : 0000000000000001 r30 : 0000000000000000 r31 : 0000000001584ab1 Call Trace: [<e0000000044159a0>] sp=0xe000000035a6f830 bsp=0xe000000035a696e0 sh ow_stack [kernel] 0x80 [<e0000000044326f0>] sp=0xe000000035a6fa00 bsp=0xe000000035a696b8 die [kernel] 0 x1b0 [<e000000004452a90>] sp=0xe000000035a6fa00 bsp=0xe000000035a69660 ia64_do_page_f ault [kernel] 0x350 [<e00000000440ea60>] sp=0xe000000035a6fa90 bsp=0xe000000035a69660 ia64_leave_ker nel [kernel] 0x0 [<e0000000044e55a0>] sp=0xe000000035a6fc30 bsp=0xe000000035a69610 kfree [kernel] 0xe0 [<a0000000005461b0>] sp=0xe000000035a6fc40 bsp=0xe000000035a695b8 gfs_pull_tail [gfs] 0x350 [<a0000000005466c0>] sp=0xe000000035a6fc40 bsp=0xe000000035a694f8 gfs_log_reserv [gfs] 0x380 [<a00000000056cc70>] sp=0xe000000035a6fc90 bsp=0xe000000035a694a8 gfs_trans_begi n [gfs] 0x290 [<a0000000005016d0>] sp=0xe000000035a6fc90 bsp=0xe000000035a69410 do_do_write [g fs] 0x130 [<a000000000502200>] sp=0xe000000035a6fcb0 bsp=0xe000000035a693a0 do_write [gfs] 0x200 [<a0000000004fe890>] sp=0xe000000035a6fcb0 bsp=0xe000000035a69328 gfs_walk_vma [ gfs] 0x1f0 [<a000000000502470>] sp=0xe000000035a6fd60 bsp=0xe000000035a692e8 gfs_write [gfs ] 0x170 [<e00000000451c0a0>] sp=0xe000000035a6fd60 bsp=0xe000000035a69290 fallback_readv _writev [kernel] 0xc0 [<e00000000451c600>] sp=0xe000000035a6fd60 bsp=0xe000000035a69238 do_readv_write v [kernel] 0x4e0 [<e00000000451c8b0>] sp=0xe000000035a6fde0 bsp=0xe000000035a691c0 sys_writev [kernel] 0xf0 [<e00000000445b290>] sp=0xe000000035a6fde0 bsp=0xe000000035a69150 sys32_writev [kernel] 0x90 [<e0000000044563c0>] sp=0xe000000035a6fe60 bsp=0xe000000035a69150 ia32_ret_from_syscall [kernel] 0x0 Kernel panic: Fatal exception I've put fixes for this into the RHEL4, FC4, and HEAD branches of cluster. I'm going to wait until the meeting tomorrow before I check them into RHEL4U1 or RHEL3. oh, in case anyone was wondering. I allocated a static variable that got put on a linked list, and worked on later, causing all sorts of pain. The fix simply changes the variable to a dynamically allocated one. This had been verified a long time ago. This bugzilla is reported to have been fixed years ago. |