Re: [PATCH] Still a mm bug in the fork error path

[Pavel Machek]

Hi!

> In my kernel, it was a SIGKILL to a forking kernel thread that caused 
> the problem. While I see SIGKILLs being sent to some kernel threads, I 
> don't know if any of the kernel threads ever fork. If they don't, 
> barring a demented root user sending SIGKILLs to kernel threads, I don't 
> know if anyone else will ever see this. So, I don't have any problems 
> with it being fixed post 2.6.9.

Actually I do not think that root sending SIGKILLs to kernel threads
is demented... I tried to recover broken machine by SIGKILLing
kacpid. It did not work, so I just reniced it to get machine back.

								Pavel
PS: BTW it was evo n620c. There's something wrong with thermal
handling after swsusp. Evo will not die by overheat, but it almost
damaged machine it was standing on... ouch. Cover got deformed by
heat (quite a bit), fortunately it returned to previous shape when it
cooled down. 

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/