Re: MIPS: return after handling coprocessor 2 exception

[Gleb O. Raiko]

On 17.06.2010 21:13, David Daney wrote:
> On 06/17/2010 06:25 AM, Jesper Nilsson wrote:
> > Breaking here dropped us to the default code which always sends
> > a SIGILL to the current process, no matter what the CU2 notifier says.
> >
> > Signed-off-by: Jesper Nilsson<jesper@xxxxxx>
[...]
> > case 2:
> > raw_notifier_call_chain(&cu2_chain, CU2_EXCEPTION, regs);
> > - break;
> > + return;
>
> What happens when the call chain is empty, and the proper action *is*
> SIGILL?

It's never empty, in fact. The default notifier declared at top of 
traps.c sends SIGILL. The problem that current code is sending SIGILL in 
all cases.

Gleb.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/