Bug 418231
Summary: | ppc64: utrace(?): Stack overflows on ptrace testsuite | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jan Kratochvil <jan.kratochvil> | ||||
Component: | kernel | Assignee: | Roland McGrath <roland> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 5.1 | CC: | kernel-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | ppc64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-03-18 04:48:59 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
Jan Kratochvil
2007-12-10 16:04:42 UTC
Created attachment 282881 [details]
ppc64 stack increase 4x (from 16KB to 64KB)
As 2.6.18-58.el5.utrace2ppcstack4x.ppc64 crashed in RHTS Job 11941 increasing the stack size is probably not a solution. But it delays the crash a lot. x86 stack overflow patch: http://people.redhat.com/jkratoch/kernel-stackoverflow-x86-2005.patch x86_64 stack overflow patch (simple): http://people.redhat.com/jkratoch/kernel-stackoverflow-x86_64.patch This ppc64 crashing Bug is AFAIK not tracked so far for utrace so keeping this Bug open. RHTS Job 11941 - 2.6.18-58.el5.utrace2ppcstack4x: list_del corruptio RHTS Job 11921 - 2.6.18-58.el5.utrace2ppcstack2x: Unable to handle kernel paging request for data at address 0x004a8850 Faulting instruction address: 0xc000000000067784 cpu 0x0: Vector: 300 (Data Access) at [c0000000780df950] pc: c000000000067784: .copy_process+0x294/0x158c lr: c000 RHTS Job 11871 - 2.6.18-58.el5.utrace1 kernel BUG in check_dead_utrace at kernel/utrace.c:328! cpu 0x0: Vector: 700 (Program Check) at [c00000000269f7e0] pc: c0000000000ae0c4: .check_dead_utrace+0x178/0x22c lr: c0000000000aec44: .wake_quiescent+0x94/0x1dc sp: c00000000269fa60 msr: 8000000000029032 current = 0xc0000000764a5b60 paca = 0xc000000000474e00 pid = 18121, comm = late-ptrace-may kernel BUG in check_dead_utrace at kernel/utrace.c:328! enter ? for help 0:mon> RHTS Job 11868 - 2.6.18-58.el5.utrace1 Unable to handle kernel paging request for data at address 0x004a8850 Faulting instruction address: 0xc00000000006e6d8 cpu 0x1: Vector: 300 (Data Access) at [c0000000593bba70] pc: c00000000006e6d8: .do_exit+0x4cc/0xa14 lr: c00000000006e6a8: .do_exit+0x49c/0xa14 sp: c0000000593bbcf0 msr: 8000000000009032 dar: 4a8850 dsisr: 40000000 current = 0xc00000005ac57310 paca = 0xc000000000475000 pid = 2216, comm = tee enter ? for help 1:mon> RHTS Job 11852 - 2.6.18-58.el5.utrace1 Unable to handle kernel paging request for data at address 0x004a8850 Faulting instruction address: 0xc000000000067784 cpu 0x0: Vector: 300 (Data Access) at [c00000004ca1b950] pc: c000000000067784: .copy_process+0x294/0x158c lr: c000000000067664: .copy_process+0x174/0x158c sp: c00000004ca1bbd0 msr: 800000000000b032 dar: 4a8850 dsisr: 40000000 current = 0xc000000050870b40 paca = 0xc000000000474e00 pid = 2126, comm = runtests.sh enter ? for help 0:mon> RHTS Job 11791 - 2.6.18-58.el5.utrace1 Unable to handle kernel paging request for data at address 0x004a8850 Faulting instruction address: 0xc000000000067784 cpu 0x0: Vector: 300 (Data Access) at [c00000002b1eb950] pc: c000000000067784: .copy_process+0x294/0x158c lr: c000000000067664: .copy_process+0x174/0x158c sp: c00000002b1ebbd0 msr: 9000000000009032 dar: 4a8850 dsisr: 40000000 current = 0xc00000000806dce0 paca = 0xc000000000474e00 pid = 26101, comm = rhts-test-runne enter ? for help 0:mon> kernel-2.6.18-238.el5.ppc64 Red Hat Enterprise Linux Server release 5.6 (Tikanga) After 24h it still has not crashed (ibm-js22-vios-01-lp3.rhts.eng.bos.redhat.com), it may have beeen already fixed. |