Messages in this thread | | | Subject | Re: [patch] thread-aware coredumps, 2.5.43-C3 | From | Alan Cox <> | Date | 21 Oct 2002 15:29:33 +0100 |
| |
On Thu, 2002-10-17 at 17:40, Daniel Jacobowitz wrote: > My only problem with this is that you're waiting for all threads by > SIGKILLing them. If a process vforks or clones, and then the child > crashes, the parent will receive a SIGKILL - iff we are dumping core. > That's a change in behavior that seems a bit too arbitrary to me.
It also has a security impact when you construct a fork/fork/crash sequence that sends sigkill to the module loader or a kernel thread during start up that has not yet dropped its association with the user code.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |