> If you read my post, the bug is that the kernel CANNOT kill that
> process? Why? If it's really a bad process, shouldn't it be the one
> that gets killed?
> This is my question, and I don't see how the patch addresses it.
And you won't see one, either. You cannot change the
semantics of uninterruptible sleep, nor can the OOM
killer change other device driver things.
This means the OOM killer has little choice but to
"hope for the best" and pick another process if the
first process chosen can't exit.
If you think you can fix all drivers to work fine
when tasks suddenly disappear, I guess you might
wnat to create such a patch ...
-- Engineers don't grow up, they grow sideways. http://www.surriel.com/ http://kernelnewbies.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/