There is for some reason IRQ/sigio handler reentrancy. Both the debug "by hand" I stuck into irq.c and Thomas traces confirm it.
I have no clue how this is possible as the code in signal.c should guard against that. I will sleep on it and try to tackle this tomorrow - no idea what is going on, but this is what is happening here. A. On 11/11/15 21:49, st...@nixia.no wrote: >> I will probably add some "manual" debug code to check if the nested >> invocation happens with the debug options off. > Might be timing dependent and/or issue with nested blocking/unblocking > of signals. > Or debug printing when it should not. > > Just my two cents > > Stian Skjelstad > > > ------------------------------------------------------------------------------ > _______________________________________________ > User-mode-linux-devel mailing list > User-mode-linux-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel > ------------------------------------------------------------------------------ _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
