More details:
> $C
ffffff001f630da0 fuword16+0x4f()
ffffff001f630e10 cred2ucred+0x12b(ffffff05078c7098, 426d, 0, ffffff04e6362a88)
ffffff001f630e50 door_ucred+0xbe(806b770)
ffffff001f630ec0 doorfs32+0x78(806b770, 0, 0, 0, 0, 9)
ffffff001f630f10 sys_syscall32+0xff()
> *panic_thread$<thread !grep t_procp
t_procp = 0xffffff04ea729e18
> 0xffffff04ea729e18::ps
S PID PPID PGID SID UID FLAGS ADDR NAME
R 17 1 17 17 15 0x52000000 ffffff04ea729e18 dlmgmtd
> *panic_thread::findstack
stack pointer for thread ffffff04ef6d4780: ffffff001f6309f0
ffffff001f630ae0 panic+0x94()
ffffff001f630b70 die+0xdd()
ffffff001f630c80 trap+0x177e()
ffffff001f630c90 0xfffffffffb8001d6()
ffffff001f630da0 fuword16+0x4f()
ffffff001f630e10 cred2ucred+0x12b()
ffffff001f630e50 door_ucred+0xbe()
ffffff001f630ec0 doorfs32+0x78()
ffffff001f630f10 sys_syscall32+0xff()
Do you think it's still the same issue? If so, is there any workaround
for that?
Thanks,
On Tue, Jun 15, 2010 at 2:31 PM, <[email protected]> wrote:
>
>>Hi,
>>
>>Anyone saw that before on snv_129?
>
> Likely:
>
> 6923355 tcp leaves conn_ixa->ixa_cred unitialized causing confusion
>
> aka
>
> 6915516 panic in supgroupmember, snv_130
>
> by holding on to a freed credential and using it caused corruption in
> memory allocated.
>
> Fixed in build 135 (and also in 134a/134b)
>
> Casper
>
>
--
Piotr Jasiukajtis | estibi | SCA OS0072
http://estseg.blogspot.com
_______________________________________________
networking-discuss mailing list
[email protected]
