What is the kdb equivalent of access_ok()? I got this crash this morning
with our SP3 kernel. It seems there are alot of places where the pointer
is not checked before dereferencing it.
I have to fix that.
SysRq : Entering kdb
Entering kdb (current=0xc0000000078a7510, pid 1234) on processor 0 due to
Keyboard Entry
[0]kdb> bt 72
SP(esp) PC(eip) Function(args)
0x0000000000000048 0x0000000000000000
kdb: Debugger re-entered on cpu 0, new reason = 7
Forced recursion is set
Attempting recursive mode
Entering kdb (current=0xc0000000078a7510, pid 1234) on processor 0 due to
Recursion @ 0xc000000000056f74
[0]kdb> bt
Stack traceback for pid 1234
0xc0000000078a7510 1234 1 1 0 R 0xc0000000078a79c0 *khvcd
SP(esp) PC(eip) Function(args)
0xc00000000789f330 0xc000000000056f74 .task_curr +0x1c
0xc00000000789f330 0xc0000000000519ec (lr) .kdba_bt_stack_ppc +0x1c4
0xc00000000789f370 0xc000000000051908 .kdba_bt_stack_ppc +0xe0
0xc00000000789f610 0xc000000000051da0 .kdba_bt_address +0x24
0xc00000000789f680 0xc000000000221fc4 .kdb_bt +0x400
0xc00000000789f7b0 0xc000000000228f0c .kdb_parse +0x3e4
0xc00000000789f880 0xc00000000022ae7c .kdb_main_loop +0xa78
0xc00000000789f980 0xc0000000000567e0 .kdba_main_loop +0x84
0xc00000000789fb80 0xc000000000227f50 .kdb +0x5b4
0xc00000000789fc50 0xc000000000054cc0 .sysrq_handle_kdb +0x28
0xc00000000789fce0 0xc000000000266c18 .__handle_sysrq_nolock +0x110
0xc00000000789fd90 0xc000000000267054 .handle_sysrq +0x7c
0xc00000000789fe30 0xc000000000267cbc .khvcd +0x2d4
0xc00000000789ff90 0xc000000000017cdc .kernel_thread +0x4c
[0]kdb>
[0]kdb> go
kdb: Debugger re-entered on cpu 0, new reason = 7
Not executing a kdb command
No longjmp available for recovery
Forced recursion is set
Attempting recursive mode
--
short story of a lazy sysadmin:
alias appserv=wotan
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
