Re: [oom]: [0/4] fix OOM deadlock running OAST

[Andrew Morton]

William Lee Irwin III <wli@xxxxxxxxxxxxxx> wrote:
>
> While running OAST to test 2.6's maximum client capacity, the kernel
> deadlocked instead of properly OOM'ing. The obvious cause was the
> line if (nr_swap_pages > 0) in out_of_memory(), which fails to account
> for pinned allocations. This can't simply be removed.

It all seems like rather a lot of fuss.

It should be the case that zone->all_unreclaimable is set by the time this
happens.  Did you consider feeding that into the oom-killing decision
instead?
-
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/