Re: PTRACE_SEIZE should not stop [Re: [PATCH 02/11] ptrace:implement PTRACE_SEIZE]

[Jan Kratochvil]

Hi Tejun,

On Mon, 16 May 2011 15:45:10 +0200, Tejun Heo wrote:
> I don't think INTERRUPT can be prioritized like that above existing
> trap conditions.  Traps are taken sometimes deep in the kernel
> (e.g. fork/exec) and often after modifying states irrevocably
> (e.g. signal is already dequeued on signal trap).  I don't think how
> it would be possible to rewind the state changes and replay it later.

OK, so that closes one of the major issues I was trying to get "fixed".


Thanks for info,
Jan
--
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/