Oddity. I'm seeing SIGFPEs arrive in the wrong process. I'm seeing this in my 2.4.x kernels, on 8260 and 750 cpus (and anything else that has an FPU).
Example programs attached. Run 'someFPU' in an xterm. Run 'corruptFPSCR' in another. Watch 'someFPU' die. Is this a similar issue to the fast-syscall-return FPU path bug that troubled the ia64 port? (and yes, 'corruptFPSCR' is pathological, but so are most denial-of-service exploits) -- Jason McMullan <jason.mcmullan at timesys.com> TimeSys Corporation -------------- next part -------------- A non-text attachment was scrubbed... Name: someFPU.c Type: text/x-c Size: 271 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20040616/f0ea0099/attachment.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: corruptFPSCR.c Type: text/x-c Size: 631 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20040616/f0ea0099/attachment-0001.bin
