Messages in this thread | | | Date | Tue, 13 Aug 2002 13:42:19 -0700 (PDT) | From | Linus Torvalds <> | Subject | Re: [patch] exit_free(), 2.5.31-A0 |
| |
On Tue, 13 Aug 2002, Ingo Molnar wrote: > > a quick workaround is in the attached patch but it's an incorrect fix: > kmod does not want to receive any signals from the helper thread for a > reason - it can be executed from any process context, correct? I dont know > how this should be fixed.
Hmm.. The workarounds make me suspect that maybe your right interface was the right one after all.
This interface has the advantage that the exit() path for this kind of child has _zero_ context switching overhead etc, so I do like it. Although I get this feeling that the release_task() issue would be much more cleanly handled by just letting schedule_tail() do the last "put_task()", the same way we handle the pending MM issue..
Maybe the best approach is to really mix the two approaches: a separate clone flag to say that the parent really doesn't care about waiting for the thing, but do it this way (so that init doesn't have to spend time cleaning up either).
Linus
- 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/
| |