On Mon, May 09, 2011 at 06:58:57PM +0200, Oleg Nesterov wrote:> Right now I am a bit puzzled why do we have 2 bits, JOBCTL_TRAP_INTERRUPT> and JOBCTL_TRAP_SEIZE... But I didn't read this + other patches yet.

It eventually ends up with three trap flags - SEIZE, INTERRUPT andNOTIFY. They all use PTRACE_EVENT_INTERRUPT trap but are different asfor when they're cleared. SEIZE is cleared after any trap. INTERRUPTis cleared after an INTERRUPT trap and NOTIFY is cleared afterGETSIGINFO. We can add different pending flags and adjust INTERRUPTflag according to different pending conditions but I think it'scleaner to have multiple trap flags than multiplexing things oversingle trap flag.

> At first glance, JOBCTL_TRAP_INTERRUPT has the same problem with the> killed tracee. I think this is easy to fix.